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)


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

If anybody is missing something, it must be me. This is all new
territory to me. I'd be interested in seeing how Nathan did it for
NetBSD, that would give me some clues. But I think I also need to
look closer at the NPTL and core files... I'm still not sure that
doing what I want to do will be possible at all.

-- 
Joel


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