This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: GDB doesn't display thread_id while debugging a core file

On Mon, 2008-04-14 at 18:01 -0700, Icarus Sparry wrote:
> Last November there was some discussion on this topic, which ended with
> Daniel Jacobowitz saying in
> 	If we assume that the host's libthread_db will either recognize
> the
> 	core file and do the right thing, or reject the core file, then
> we can
> 	write a small target layer that uses it on top of corelow.c in a
> 	similar way to how linux-thread-db.c / proc-service.c use
> linux-nat.c.
> 	It's just a matter of testing that on a couple of different
> setups,
> 	like LinuxThreads and cross debuggers, to see how it behaves.
> Or
> 	doesn't behave.
> Being able to access variables declared with __thread in core files
> would certainly be useful. Could someone give some reasonable guess of
> the amount of effort required to do this? In particular for a powerpc32
> corefile from a linux process with NPTL being debugged on an x86 linux
> box.

Off hand, I would not expect the libthread_db library to 
be able to do anything useful with a corefile from a different

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]