From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: RFC: Initialize libthread_db at the right time
Date: Thu, 30 Mar 2006 16:47:00 -0000 [thread overview]
Message-ID: <20060330163437.GC32409@nevyn.them.org> (raw)
In-Reply-To: <20060227194414.GA26229@nevyn.them.org>
On Mon, Feb 27, 2006 at 02:44:14PM -0500, Daniel Jacobowitz wrote:
> We've had some recurring problems debugging statically linked executables
> using libthread_db; this patch is the first of several fixes for that.
> This doesn't do much; it just splits the check out from the new_objfile
> hook, and calls it from target_post_attach and target_post_startup_inferior
> in the Linux native target.
>
> Earlier versions of this patch used an observer instead, which was silly
> of me; we only want to do this when we're sitting on top of the Linux
> native target, not when we're on top of e.g. the remote target. This
> mostly fixes the not-enabling-libthread_db-when-we-should-be class of
> problems; there's still one gross hack in remote.c which avoids
> calling the new objfile hook for remote targets, but that's a mess
> for another day.
>
> Any comments? Otherwise, I'll commit this in a few days. It handles
> LinuxThreads, but NPTL needs a little push (coming up next).
OK, more than a few days. And the NPTL push never got pushed, because
the glibc maintainers didn't like my solution, but have not suggested
an alternative yet. I'll poke them again.
This part committed.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-03-30 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 19:59 Daniel Jacobowitz
2006-03-01 21:39 ` Michael Snyder
2006-03-30 16:47 ` Daniel Jacobowitz [this message]
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=20060330163437.GC32409@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.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