This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/3426] canonicalize_file_name's behavior differs from documentation
- From: "lemke_juergen at yahoo dot de" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 26 Oct 2006 20:13:44 -0000
- Subject: [Bug libc/3426] canonicalize_file_name's behavior differs from documentation
- References: <20061026053818.3426.lemke_juergen@yahoo.de>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From lemke_juergen at yahoo dot de 2006-10-26 20:13 -------
Hello,
jakub at redhat dot com wrote:
> __nonnull ((1)) means that the first argument must
> not be NULL, not that
> the function can't return NULL.
That is not what I was referring to. Just above the declaration of
canonicalize_file_name() you can read:
"The last file name component need not exist [...]"
However, as of GNU libc 2.3.5, this function always fails (returning NULL) when
passed a path to a inexistent file.
Best,
Juergen
--
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |
http://sourceware.org/bugzilla/show_bug.cgi?id=3426
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.