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: "jan dot kratochvil at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 19 Nov 2009 09:56:38 -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 jan dot kratochvil at redhat dot com 2009-11-19 09:56 -------
(In reply to comment #2)
> Someone might want to test where the RT_CONSISTENT breakpoint happens in
> relation to relocation on Solaris.
Verified by Paul Pluzhnikov
https://bugzilla.redhat.com/show_bug.cgi?id=179072#c15
I can't find official documentation for RT_CONSISTENT,
but Solaris (from which this interface is copied) AFAICT calls
_dl_debug_state() (or rather its Solaris equivalent) at (B):
http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/sgs/rtld/common/setup.c#1028
[ (B) = after relocations and before initializers ]
> AFAICT the RT_CONSISTENT state is purely about the state of the r_debug.r_map
> list and all those pointers. It says you can get the list of objects mapped
> in core now, that is all.
There is just no easy way for debugger how to catch the later point - after the
relocations got resolved.
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |ppluzhnikov at google dot
| |com
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.