This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/13097] gdb regression: Excessive linux-vdso.so.1 name
- From: "carlos at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 28 May 2013 20:02:16 +0000
- Subject: [Bug libc/13097] gdb regression: Excessive linux-vdso.so.1 name
- Auto-submitted: auto-generated
- References: <bug-13097-131 at http dot sourceware dot 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.