This is the mail archive of the gdb-patches@sources.redhat.com 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: thread ptids when debugging from core file (x86-linux)


On Fri, Aug 06, 2004 at 10:58:18AM -0700, Joel Brobecker wrote:
> > >I've always assumed that corelow.c's mapping between .reg sections and
> > >threads was intended as a minimal fallback. The module I wrote for
> > >NetBSD's threads (which I'll get into shape for the FSF tree Real Soon
> > >Now) punts that list and generates its own list of threads from the
> > >memory structures of libpthread in the core file, just as it would for
> > >a live process.
> > 
> So do you think I'll have to dig into the inferior memory for data used
> by the libpthread library to find that information? Is this something
> that would be portable across NPTL versions? Supposing we want to go
> that route, does anybody know where to find some documentation (or some
> code) that exposes the data structures, so I can try digging into them?

[not strictly Linux, but more genericly]

But how do you map register contents in the various .reg/# sections to
the right thread if there's no way to correlate .reg/# sections to light-
weight processes? Would this in fact imply that the IDs needs to match?

Or am I missing something here?

-- 
 Marcel Moolenaar	  USPA: A-39004		 marcel@xcllnt.net


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