public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppluzhnikov at google dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/13895] New: SIGSEGV in __nss_lookup_function for static binary when configured with --enable-static-nss Date: Fri, 23 Mar 2012 17:11:00 -0000 [thread overview] Message-ID: <bug-13895-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=13895 Bug #: 13895 Summary: SIGSEGV in __nss_lookup_function for static binary when configured with --enable-static-nss Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: unassigned@sourceware.org ReportedBy: ppluzhnikov@google.com CC: drepper.fsp@gmail.com Classification: Unclassified Created attachment 6299 --> http://sourceware.org/bugzilla/attachment.cgi?id=6299 proposed patch Original report: http://sourceware.org/ml/libc-alpha/2012-03/msg00080.html Reproduces with current git: commit 3ff4252677ff55a0dd4ded5b5cbccda25812ba12 Author: Paul Pluzhnikov <ppluzhnikov@google.com> Date: Fri Mar 23 09:47:03 2012 -0700 cat t.c #include <sys/types.h> #include <pwd.h> int main() { struct passwd *pw = getpwnam("root"); return 0; } gcc -g -L. -static t.c gdb -q ./a.out Reading symbols from /tmp/build-static-nss/a.out...done. (gdb) r Program received signal SIGSEGV, Segmentation fault. 0x0000000000410878 in __nss_lookup_function (ni=0x6e5f50, fct_name=0x4af0df "getpwnam_r") at nsswitch.c:460 460 size_t namlen = (5 + strlen (ni->library->name) + 1 (gdb) bt #0 0x0000000000410878 in __nss_lookup_function (ni=0x6e5f50, fct_name=0x4af0df "getpwnam_r") at nsswitch.c:460 #1 0x0000000000410a6e in __nss_lookup (ni=0x7fffffffd4e8, fct_name=0x4af0df "getpwnam_r", fct2_name=0x0, fctp=0x7fffffffd4e0) at nsswitch.c:161 #2 0x000000000040e416 in __getpwnam_r (name=0x4abf84 "root", resbuf=0x6e0ce0, buffer=0x6e5840 "", buflen=1024, result=0x7fffffffd538) at ../nss/getXXbyYY_r.c:202 #3 0x000000000040e12c in getpwnam (name=0x4abf84 "root") at ../nss/getXXbyYY.c:116 #4 0x0000000000400e76 in main () at t.c:6 (gdb) p ni.library $1 = (service_library *) 0x0 (gdb) p ni.name $2 = 0x6e5f80 "files" -- 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 reply other threads:[~2012-03-23 17:09 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-23 17:11 ppluzhnikov at google dot com [this message] 2012-03-23 19:17 ` [Bug libc/13895] " ppluzhnikov at google dot com 2012-04-06 20:56 ` ppluzhnikov at google dot com 2014-06-26 13:44 ` 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-13895-131@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: linkBe 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).