Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Nathan J. Williams" <nathanw@wasabisystems.com>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: thread ptids when debugging from core file (x86-linux)
Date: Fri, 06 Aug 2004 04:40:00 -0000	[thread overview]
Message-ID: <mtu3c30swux.fsf@contents-vnder-pressvre.mit.edu> (raw)
In-Reply-To: <20040806040959.GL1192@gnat.com>

Joel Brobecker <brobecker@gnat.com> writes:

> According to corelow.c:add_to_thread_list(), the thread PTID
> is a degenerated {pid, 0, 0} where pid is just the number in the section
> name where the thread has been dumped (ie section ".reg/1234" => thread
> ptid = {1234, 0, 0}).

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.

        - Nathan


  reply	other threads:[~2004-08-06  4:40 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 [this message]
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
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=mtu3c30swux.fsf@contents-vnder-pressvre.mit.edu \
    --to=nathanw@wasabisystems.com \
    --cc=brobecker@gnat.com \
    --cc=gdb-patches@sources.redhat.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