From: Randolph Chung <randolph@tausq.org>
To: gdb@sources.redhat.com
Subject: Question about _dl_debug_state and new glibc
Date: Mon, 11 Oct 2004 18:54:00 -0000 [thread overview]
Message-ID: <20041011172207.GA14151@tausq.org> (raw)
Hi all,
I've been away from gdb for a bit, so hopefully this is not something
simple I missed while I've been away :)
It appears that newer versions of glibc now marks the _dl_debug_state
function as hidden, making it not visible to gdb. This breaks the
solib tracking code in solib-svr4.c.....
Looking at the docs, it looks like the "proper" way for gdb to do this
is to look up the r_debug symbol and use the r_brk member to locate
_dl_debug_state's address. is there any particular reason why we don't
do this in gdb?
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
next reply other threads:[~2004-10-11 17:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 18:54 Randolph Chung [this message]
2004-10-11 19:03 ` Kevin Buettner
2004-10-11 19:14 ` Daniel Jacobowitz
2004-10-11 20:47 ` Mark Kettenis
2004-10-12 6:57 ` Daniel Jacobowitz
2004-10-11 22:00 ` Kevin Buettner
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=20041011172207.GA14151@tausq.org \
--to=randolph@tausq.org \
--cc=gdb@sources.redhat.com \
/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