public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "geir at cray dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/12491] Calling getpwuid in a statically linked program should return an error, not a seg fault.
Date: Thu, 15 Sep 2011 16:15:00 -0000	[thread overview]
Message-ID: <bug-12491-131-H1nFT8xj0u@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12491-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=12491

--- Comment #3 from Geir Johansen <geir at cray dot com> 2011-09-15 16:14:45 UTC ---
(In reply to comment #2)
> getpwuid works just fine under the only conditions when it can work, just as
> described in the link message.  If you overlook that message it is your
> problem.

My editorial comment on this resolution:

If the nscd daemon is running on the system, the program will run fine without
problems.

If the nscd daemon is not running on the system, the program will get a
segmentation fault and the user will not have any idea why the program is
failing. In my opinion this behavior is unacceptable. The library should be
more robust and at the very least report an error in this case.

-- 
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.


  parent reply	other threads:[~2011-09-15 16:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14 23:32 [Bug libc/12491] New: " geir at cray dot com
2011-03-04 23:55 ` [Bug libc/12491] " geir at cray dot com
2011-04-18  2:26 ` drepper.fsp at gmail dot com
2011-09-15 16:15 ` geir at cray dot com [this message]
2014-06-27 13:51 ` fweimer at redhat dot com
2021-09-12 16:46 ` ovilewade9 at gmail 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-12491-131-H1nFT8xj0u@http.sourceware.org/bugzilla/ \
    --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).