From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com, msnyder@redhat.com
Subject: Re: [rfa] Include the LWP in thread-db's PTIDs
Date: Mon, 11 Oct 2004 16:17:00 -0000 [thread overview]
Message-ID: <416AB1EE.9000706@gnu.org> (raw)
In-Reply-To: <20041011153838.GA26796@nevyn.them.org>
> I hadn't thought about the core issue; I'll do some pondering. However,
> I don't think your comment is quite right. Thread_db can not be
> layered over core files, we've already decided that - it's too iffy to
> find the right thread_db, not to mention cross-debugging issues. And
> similarly we can't use it for remote thread debugging. Thread_db only
> makes any sense on top of local, running, native threads.
"we"'ve definitly not decided this.
Long ago you committed a hack to stop GDB layering thread-db over core
files. It was to stop GDB barfing on native GNU/Linux core files. It
had the side effect of breaking threads on all other systems, namely
solaris. What keeps being pointing out is that thread-db should be
loaded over a core file, and not doing it is broken.
If we try it and it barfs, we've a bug. But what we've not got is an
excuse for hobble native support (just because embedeed debuging is "iffy").
Andrew
next prev parent reply other threads:[~2004-10-11 16:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-10 21:36 Daniel Jacobowitz
2004-10-11 15:29 ` Andrew Cagney
2004-10-11 15:38 ` Daniel Jacobowitz
2004-10-11 15:55 ` Joel Brobecker
2004-10-11 16:17 ` Andrew Cagney [this message]
2004-10-11 17:12 ` Daniel Jacobowitz
2004-10-11 18:29 ` Andrew Cagney
2004-10-12 13:26 ` Daniel Jacobowitz
2004-10-11 19:40 ` Mark Kettenis
2004-10-12 13:31 ` Daniel Jacobowitz
2004-10-13 21:16 ` Mark Kettenis
2004-10-13 21:27 ` Daniel Jacobowitz
2004-10-17 19:19 ` Daniel Jacobowitz
2004-10-13 21:37 ` Paul Gilliam
2004-11-14 19:17 ` Daniel Jacobowitz
2004-12-02 21:16 ` Michael Snyder
2004-12-08 16:14 ` Daniel Jacobowitz
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=416AB1EE.9000706@gnu.org \
--to=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@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