From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Snyder <msnyder@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Don't use thread_db on corefiles
Date: Thu, 13 Dec 2001 15:57:00 -0000 [thread overview]
Message-ID: <20011213185635.A12902@nevyn.them.org> (raw)
In-Reply-To: <3C193D13.AED0F79F@cygnus.com>
On Thu, Dec 13, 2001 at 03:43:15PM -0800, Michael Snyder wrote:
> Good, dumping only the LWPs is the right thing to do, I think.
> But if that's what you're doing, then the thread-db module should
> still be useful to you: I know it is on Solaris, which this one
> was modelled after. You'll need it if-and-when the thread-to-lwp
> mapping ever becomes many-to-one (which may be soon).
See my comments about cross core debugging in my message to Andrew.
> > So there is enough information there for lin-lwp to parse the threads,
> > if we stubbed out its attempts to write, I expect. But since the
> > current Linux threads model has one thread per process, I can simply
> > use the corefile.c thread support instead, which I'd rather do.
>
> You can't rely on that assumption in the future. We need to make
> all these packages work together. It won't be a freebie, it will
> require some work. But as I say, it works for Solaris gdb. We
> just didn't bother making it work for Linux gdb and corefiles,
> because up until now there were no threads in corefiles on Linux.
It will require a large amount of work. For now, threaded core dumps
work with cross debuggers (because thread_db and lin-lwp are not
present at all) but cause internal errors with native debuggers for the
reasons I explained. If there is really such vehement opposition to my
workaround, I'll maintain it as a local patch instead, and leave anyone
else wanting to do this out in the cold. Please don't take that as any
kind of threat; the patch fixes something which is obviously broken,
and I can not justify the time for the significant infrastructure work
necessary for any other solution.
Thread_db, as things stand, does not work on core files. Is preventing
it from trying, and thus crashing GDB, really such a disruptive
suggestion?
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-12-13 23:57 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-13 8:50 Daniel Jacobowitz
2001-12-13 10:57 ` Andrew Cagney
2001-12-13 11:37 ` Daniel Jacobowitz
2001-12-16 17:58 ` Daniel Jacobowitz
2001-12-16 21:32 ` Kevin Buettner
2001-12-17 8:34 ` Daniel Jacobowitz
2001-12-13 12:26 ` Michael Snyder
2001-12-13 12:31 ` Daniel Jacobowitz
2001-12-13 14:59 ` Michael Snyder
2001-12-13 15:04 ` Daniel Jacobowitz
2001-12-13 15:08 ` Michael Snyder
2001-12-13 15:11 ` Daniel Jacobowitz
2001-12-13 15:37 ` Andrew Cagney
2001-12-13 15:46 ` Daniel Jacobowitz
2001-12-13 17:14 ` Michael Snyder
2001-12-13 20:29 ` Daniel Jacobowitz
2001-12-14 18:12 ` Andrew Cagney
2001-12-14 18:25 ` Daniel Jacobowitz
2001-12-13 15:47 ` Michael Snyder
2001-12-13 15:57 ` Daniel Jacobowitz [this message]
2001-12-13 16:06 ` Daniel Jacobowitz
2001-12-13 17:31 ` Michael Snyder
2001-12-13 20:23 ` Daniel Jacobowitz
2001-12-14 15:43 ` Michael Snyder
2001-12-14 17:14 ` Daniel Jacobowitz
2001-12-17 11:40 ` Michael Snyder
2001-12-17 11:51 ` Daniel Jacobowitz
2001-12-13 17:26 ` Michael Snyder
2001-12-13 20:27 ` Daniel Jacobowitz
2001-12-14 18:31 ` Andrew Cagney
2001-12-14 18:36 ` Andrew Cagney
2001-12-14 18:42 ` Daniel Jacobowitz
2001-12-15 9:16 ` Andrew Cagney
2001-12-16 12:26 ` Daniel Jacobowitz
2001-12-16 13:29 ` Andrew Cagney
2001-12-16 17:02 ` Daniel Jacobowitz
2002-01-03 17:11 ` Michael Snyder
2002-01-04 10:25 ` Daniel Jacobowitz
2002-01-04 14:49 ` Michael Snyder
2002-01-04 17:28 ` Michael Snyder
2002-01-04 17:47 ` 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=20011213185635.A12902@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@cygnus.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