From: Daniel Jacobowitz <drow@false.org>
To: Kevin Buettner <kevinb@redhat.com>
Cc: Randolph Chung <randolph@tausq.org>, gdb@sources.redhat.com
Subject: Re: Question about _dl_debug_state and new glibc
Date: Mon, 11 Oct 2004 19:14:00 -0000 [thread overview]
Message-ID: <20041011175524.GA29450@nevyn.them.org> (raw)
In-Reply-To: <20041011104647.6a03d9ce@saguaro>
On Mon, Oct 11, 2004 at 10:46:47AM -0700, Kevin Buettner wrote:
> On Mon, 11 Oct 2004 10:22:07 -0700
> Randolph Chung <randolph@tausq.org> wrote:
>
> > 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?
Only for static executables usually; for dynamic executables it's
supposed to be DT_DEBUG if that's available. Same difference.
> I can't think of any reason. I'm guessing that it was more expedient
> for the original authors of the code to do it the way it was done.
> In any case, I know of no reason not to change it so that it's done
> "properly".
We set the breakpoint on _dl_debug_state before starting the inferior.
_dl_debug_initialize initializes _r_debug somewhat later... I'm not
sure how it is supposed to be used. Do either of you know?
I see it hasn't been exported since March. Blech.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-10-11 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 18:54 Randolph Chung
2004-10-11 19:03 ` Kevin Buettner
2004-10-11 19:14 ` Daniel Jacobowitz [this message]
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=20041011175524.GA29450@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=kevinb@redhat.com \
--cc=randolph@tausq.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).