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/13097] gdb regression: Excessive linux-vdso.so.1 name
Date: Tue, 28 May 2013 20:02:00 -0000 [thread overview]
Message-ID: <bug-13097-131-atGP4GdQuA@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13097-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13097
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |WAITING
CC| |carlos at redhat dot com
--- Comment #5 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Samuel Bronson from comment #4)
> This is still an issue; how could listing a library under a valid but
> non-existent filename not confuse tools?
We aren't likely to get to work on this any time soon. We don't have enough
resources.
The code in question is now in elf/setup-vdso.h, and I would be more than happy
to review a patch that fixes this bug.
You'd need to run the testsuite on master to make sure you don't introduce any
regressions and then show that LD_DEBUG=all still works, and that the debugger
which was previously reporting bogus warnings doesn't report any more bogus
warnings.
The best possible patch avoids this hack:
+ if (GLRO(dl_debug_mask))
+ l->l_name = copy;
and instead adjusts the debug code to inform the user that this DSO has no
associated file e.g. a virtual dso.
Notes:
http://sourceware.org/glibc/wiki/Contribution%20checklist
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-05-28 20:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 12:36 [Bug libc/13097] New: " jan.kratochvil at redhat dot com
2011-09-06 1:39 ` [Bug libc/13097] " drepper.fsp at gmail dot com
2012-08-14 12:54 ` jan.kratochvil at redhat dot com
2012-11-24 19:10 ` jan.kratochvil at redhat dot com
2012-11-24 21:40 ` ldv at altlinux dot org
2013-05-27 21:10 ` naesten at gmail dot com
2013-05-28 20:02 ` carlos at redhat dot com [this message]
2013-06-09 3:26 ` naesten at gmail dot com
2014-02-07 2:57 ` [Bug dynamic-link/13097] " jsm28 at gcc dot gnu.org
2014-02-16 17:50 ` jackie.rosen at hushmail dot com
2014-02-20 7:21 ` kalvdans at gmail dot com
2014-03-24 1:24 ` ovidiu.b13 at gmail dot com
2014-05-28 19:41 ` schwab at sourceware dot org
2014-06-27 12:25 ` 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-13097-131-atGP4GdQuA@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).