From: Joel Brobecker <brobecker@gnat.com>
To: Marcel Moolenaar <marcel@xcllnt.net>
Cc: Andrew Cagney <cagney@gnu.org>,
"Nathan J. Williams" <nathanw@wasabisystems.com>,
gdb-patches@sources.redhat.com
Subject: Re: thread ptids when debugging from core file (x86-linux)
Date: Fri, 06 Aug 2004 18:35:00 -0000 [thread overview]
Message-ID: <20040806183557.GU1192@gnat.com> (raw)
In-Reply-To: <20040806180811.GA25829@dhcp50.pn.xcllnt.net>
> > 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
next prev parent reply other threads:[~2004-08-06 18:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-06 4:10 Joel Brobecker
2004-08-06 4:40 ` Nathan J. Williams
2004-08-06 5:39 ` Andrew Cagney
2004-08-06 17:58 ` Joel Brobecker
2004-08-06 18:08 ` Marcel Moolenaar
2004-08-06 18:35 ` Joel Brobecker [this message]
2004-08-06 19:10 ` Nathan J. Williams
2004-08-06 20:53 ` Marcel Moolenaar
2004-08-06 19:18 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040806183557.GU1192@gnat.com \
--to=brobecker@gnat.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=marcel@xcllnt.net \
--cc=nathanw@wasabisystems.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox