This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/2328] _dl_debug_state() RT_CONSISTENT called too early
- From: "drepper at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 30 Apr 2010 16:03:36 -0000
- Subject: [Bug libc/2328] _dl_debug_state() RT_CONSISTENT called too early
- References: <20060211192240.2328.jreiser@BitWagon.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From drepper at redhat dot com 2010-04-30 16:03 -------
(In reply to comment #5)
> "Nothing should prevent you inserting breakpoints before relocation, ..."
> Except that in general, being subject to future relocation *does* prevent
> inserting breakpoints.
The breakpoint could be added into the appropriate code in the dynamic linker
(i.e., the place calling the constructor for the object. That code is already
relocated.
It is wrong to change the semantics of RT_CONSISTENT. And I think it is a bad
approach trying to extend this strange interface with the debugger by adding a
RT_RUNNABLE state (I made up the name) for when the relocation happened, too.
If we need more state information it is better to expose some APIs. We have
libthread_db, maybe we need librtld_db as well. If we'd have a specification of
what information of the implementation gdb currently contains and what it still
wants we can design such a library.
I guess I am waiting for gdb people to provide this information.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
http://sourceware.org/bugzilla/show_bug.cgi?id=2328
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.