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.kratochvil at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Thu, 11 Aug 2011 11:38:42 +0000
- Subject: [Bug libc/2328] _dl_debug_state() RT_CONSISTENT called too early
- Auto-submitted: auto-generated
- References: <bug-2328-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=2328
Jan Kratochvil <jan.kratochvil at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |ASSIGNED
--- Comment #7 from Jan Kratochvil <jan.kratochvil at redhat dot com> 2011-08-11 11:38:42 UTC ---
(In reply to comment #6)
> 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.
Such breakpoint is put there by the SystemTap probes, as implemented by Gary
Benson for glibc + gdb.
> It is wrong to change the semantics of RT_CONSISTENT.
This patch does not do so.
> And I think it is a bad approach trying to extend this strange interface
Neither this one.
> If we need more state information it is better to expose some APIs. We have
> libthread_db, maybe we need librtld_db as well.
These SystemTap probes are such alternative interface but SystemTap probes
were never replied to in the mailing list:
merging roland/systemtap branch
http://sourceware.org/ml/libc-alpha/2011-03/msg00001.html
> 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.
SystemTap probes work well for this purpose.
> I guess I am waiting for gdb people to provide this information.
This patch contains the needed features.
--
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.