public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "law at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug dynamic-link/14474] New: LD_DEBUG=bindings produces incorrect data Date: Wed, 15 Aug 2012 18:48:00 -0000 [thread overview] Message-ID: <bug-14474-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=14474 Bug #: 14474 Summary: LD_DEBUG=bindings produces incorrect data Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: dynamic-link AssignedTo: unassigned@sourceware.org ReportedBy: law@redhat.com Classification: Unclassified Created attachment 6580 --> http://sourceware.org/bugzilla/attachment.cgi?id=6580 Uli's patch to fix this problem The binding information printed for LD_DEBUG=bindings is incorrect when dlopen is used. This severely hinders people debugging problems with audit modules and other problems. Steps to Reproduce: 1.find program which uses dlopen with a handle returned by dlopen 2.use LD_DEBUG=bindings 3. Actual results: The 'from' map is reported to be the map with the definition Expected results: The from 'from' map should be reported. Uli's patch for this problem is attached. I haven't evaluated either the problem or the patch. -- 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-08-15 18:48 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-15 18:48 law at redhat dot com [this message] 2013-01-15 11:22 ` [Bug dynamic-link/14474] " schwab@linux-m68k.org 2013-10-11 18:20 ` neleai at seznam dot cz 2014-06-17 18:37 ` 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-14474-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).