Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Martin Fouts" <mfouts@danger.com>
To: <gdb@sourceware.org>
Cc: "Mike Chen" <mchen@danger.com>
Subject: Why does gdb use its own thread ids internally rather than the tid from the underlying thread implementation?
Date: Mon, 03 Mar 2008 18:42:00 -0000	[thread overview]
Message-ID: <B95CEC1093787C4DB3655EF330984818051CB9@EXCHANGE.danger.com> (raw)

Hi,

We're trying to optimize the NetBSD 4.0 implementation of pthreads,
which has an M:N thread implementation, and are having some trouble
getting gdb to work because the underlying thread id for a thread can
change in an M:N implementation.

Can anyone provide any insight into why gdb doesn't use the underlying
thread id?

Or suggestions about how to accommodate M:N without zombie queues?

Thanks,

Marty


             reply	other threads:[~2008-03-03 18:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-03 18:42 Martin Fouts [this message]
2008-03-03 19:57 ` Michael Snyder
2008-03-03 20:09   ` Daniel Jacobowitz
2008-03-03 20:20   ` Why does gdb use its own thread ids internally rather than the ?tid " Mark Kettenis
2008-03-03 20:38     ` Michael Snyder
2008-03-03 20:56       ` Mark Kettenis

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=B95CEC1093787C4DB3655EF330984818051CB9@EXCHANGE.danger.com \
    --to=mfouts@danger.com \
    --cc=gdb@sourceware.org \
    --cc=mchen@danger.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