[RFA] Don't use thread_db on corefiles

[Andrew Cagney]

> On Thu, Dec 13, 2001 at 03:04:07PM -0800, Michael Snyder wrote:
> 
>> OK.  I'd like to see that patch when it's ready.
>> Do you use only lwp's, or do you use glibc/libpthread threads?
>> If you use library threads, are you saving their info in the
>> core file, or are you only saving the info for the lwp's?
> 
> 
> It's completely thread-package-agnostic.  I dump all LWPs sharing the
> same VM, as a fairly reliable marker (I'd use 2.4 threadgroups, but
> LinuxThreads doesn't use them...)


Ok.  So you're dumping out the raw data that libthread-db would use to 
recreate the current thread state from the raw LWP state.


> 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.


Er, careful.  I think lin-lwp should be fixed.  lin-lwp should be 
interpreting the raw LWP data translating it into user level threads. 
(Why it writes to the target just sounds like a bug.)

Have a look at the discussioin started by Michael on a gcore command.

Andrew