public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aurelien at aurel32 dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/2418] getcwd() print an assertion for a path greater than MAX_PATH
Date: Sat, 01 Apr 2006 21:40:00 -0000 [thread overview]
Message-ID: <20060401214006.24376.qmail@sourceware.org> (raw)
In-Reply-To: <20060305170201.2418.aurelien@aurel32.net>
------- Additional Comments From aurelien at aurel32 dot net 2006-04-01 21:40 -------
(In reply to comment #2)
> (In reply to comment #1)
> > Removing assert is almost never good. Provide a test case. Note that
> neither
> > the libc or kernel side of getcwd is architecture-speicfic. Otherwise I'll
> just
> > close the bug.
>
For the testcase, just try to build a recent coreutils (for example 5.94) on an
ia64 machine. The testsuite will fail.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=2418
------- 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-04-01 21:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-05 17:02 [Bug libc/2418] New: " aurelien at aurel32 dot net
2006-04-01 20:59 ` [Bug libc/2418] " drepper at redhat dot com
2006-04-01 21:38 ` aurelien at aurel32 dot net
2006-04-01 21:40 ` aurelien at aurel32 dot net [this message]
2006-04-01 21:51 ` schwab at suse dot de
2006-04-02 17:59 ` 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=20060401214006.24376.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).