public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/15473] null pointer handling in strcmp
Date: Thu, 16 May 2013 04:09:00 -0000 [thread overview]
Message-ID: <bug-15473-131-cHRgV4qNFc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15473-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15473
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |carlos at redhat dot com
Resolution| |WONTFIX
--- Comment #2 from Carlos O'Donell <carlos at redhat dot com> 2013-05-16 04:09:05 UTC ---
(In reply to comment #0)
> When we use strcmp(p, NULL) with Unix machine, It returns zero.
> But on Linux(glibc) it results into crash.
>
> I know in this case, the behavior of strcmp is "undefined".
> So it's not bug, but since it's useful for the user to port to Linux
> from other Unix, it would be nice to select the option etc.
This hides real bugs.
It also appears to incorrectly imply that NULL is equal to every string.
If you really want this kind of change then you need to talk to the standards
authors in the Austin Group (POSIX) and at your local ISO national body for
SC22/WG14.
Until then marking as resolved wontfix.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-05-16 4:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 3:53 [Bug libc/15473] New: " htpcucxo at yahoo dot co.jp
2013-05-16 3:55 ` [Bug libc/15473] " htpcucxo at yahoo dot co.jp
2013-05-16 3:59 ` bugdal at aerifal dot cx
2013-05-16 4:09 ` carlos at redhat dot com [this message]
2013-05-16 7:20 ` schwab@linux-m68k.org
2014-06-13 17:45 ` fweimer 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=bug-15473-131-cHRgV4qNFc@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/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).