public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lemke_juergen at yahoo dot de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/3426] canonicalize_file_name's behavior differs from documentation
Date: Thu, 26 Oct 2006 20:13:00 -0000 [thread overview]
Message-ID: <20061026201344.13164.qmail@sourceware.org> (raw)
In-Reply-To: <20061026053818.3426.lemke_juergen@yahoo.de>
------- 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.
next prev parent reply other threads:[~2006-10-26 20:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 5:38 [Bug libc/3426] New: " lemke_juergen at yahoo dot de
2006-10-26 7:13 ` [Bug libc/3426] " jakub at redhat dot com
2006-10-26 20:13 ` lemke_juergen at yahoo dot de [this message]
2006-10-26 21:16 ` ldv at altlinux dot org
2006-10-27 18:47 ` drepper at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061026201344.13164.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).