This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: getcwd() problem
On Fri, Oct 05, 2001 at 04:23:52PM +0400, egor duda wrote:
>Hi!
>
>Friday, 05 October, 2001 Yasushi Higuchi yzone@mail.raidway.ne.jp wrote:
>
>YH> I found a problem in the getcwd() function in recent snapshot.
>
>[...]
>>> char *cwd = getcwd(NULL, 256);
>[...]
>
>Single Unix Specification v2 says that "If buf is a null pointer, the
>behaviour of getcwd() is undefined."
>
>YH> Reference: FreeBSD manpages
>>>STANDARDS
>>>The getcwd() function conforms to ISO 9899: 1990 (``ISO C''). The ability
>>>to specify a NULL pointer and have getcwd() allocate memory as necessary
>>>is an extension.
>
>cygwin doesn't support this extension. it's arguable whether it should
>be added or not. code that implicitly allocates (on doesn't allocate,
>depending in parameters) memory on heap is a source of potential
>memory leaks.
It's supposed to support it, though. There is code to handle this but
recent pointer validation checks were a little too aggressive for the
getcwd case.
I've checked in a fix for this.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/