Re: [RFA] Don't use thread_db on corefiles

Daniel Jacobowitz
2001-12-14T04:27:17Z

On Thu, Dec 13, 2001 at 05:22:02PM -0800, Michael Snyder wrote:
> Daniel Jacobowitz wrote:
> >
> > 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.
>
> Oh, is that what you were talking about? Sorry, I must have been
> confused.
>
> So -- you are talking about building a single GDB that can debug
> 1) native x86 linux, and
> 2) MIPS multi-threaded linux corefiles.
>
> Is that right?

Well, that's not actually something I need to do, but I'd like it to be
possible. I only need for both native and cross-hosted debuggers to
both be able to get at the core files. But as things stand now, if we
fix thread_db to be able to do so using lin-lwp, then the native and
cross debuggers will get at the threads using completely different
interfaces. That worries me.

> Not necessarily -- but it's not a decision for one person to make,
> while no one else has access to the problem. Right now you're
> the only one with access to these new multi-threaded corefiles.
> Are the rest of us going to be seeing them soon? We might want
> to take part in deciding how best to support them.

Hopefully, you'll be seeing them soon :) I'll be publicly submitting
the patch if I find a less gross way to do it, and I'm trying.