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

[Daniel Jacobowitz <drow at mvista dot com>]

On Sat, Dec 15, 2001 at 12:15:58PM -0500, Andrew Cagney wrote:
> >Hmm, perhaps it is a native GDB looking at a threaded core file?  In 
> >>that case, yes the thread-db should drop its self on top.  If that is 
> >>causing an internal error then there is something messed up that should 
> >>be fixed.
> >
> >
> >Yes, that's where the internal error is.  They're based on the fact
> >that thread-db tries to enable event reporting, as best I can tell.
> 
> 
> Sounds like that is the bug to fix.  Enabling event reporting probably 
> doesn't make much sense when the target is lifeless.

I was about to try a patch for this when I realized that my primary
objection still holds.

This only works if you're debugging on a very similar host to the one
the core was dumped on.  If you've got, say, a glibc 2.1.3 host and are
looking at a glibc 2.2.3 core... well, you can provide target libraries
and make GDB use those, but there's no way to provide a cross
libthread_db.

Are we really comfortable with that?  This'll probably cause GDB to
misbehave in arbitrarily unpredictable ways in that circumstance.  And
we've no way to detect it that I can see.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer