Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Michael Snyder <msnyder@specifix.com>
Cc: Martin Fouts <mfouts@danger.com>,
	gdb@sourceware.org, 	Mike Chen <mchen@danger.com>
Subject: Re: Why does gdb use its own thread ids internally rather than the 	tid from the underlying thread implementation?
Date: Mon, 03 Mar 2008 20:09:00 -0000	[thread overview]
Message-ID: <20080303200917.GD19677@caradoc.them.org> (raw)
In-Reply-To: <1204574228.19253.570.camel@localhost.localdomain>

On Mon, Mar 03, 2008 at 11:57:08AM -0800, Michael Snyder wrote:
> On Mon, 2008-03-03 at 10:38 -0800, Martin Fouts wrote:
> > 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.

Hopefully, Mark Kettenis will have some advice on this.  The threading
code is platform-specific, and I'm not familiar with any of the BSD ports.

> > Or suggestions about how to accommodate M:N without zombie queues?
> 
> Have you looked at the linux and solaris implementations?
> They both have M:N thread models.

Not any more.  Linux support for M:N was removed, since it did not
work and there were no viable M:N implementations to test with.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-03-03 20:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-03 18:42 Martin Fouts
2008-03-03 19:57 ` Michael Snyder
2008-03-03 20:09   ` Daniel Jacobowitz [this message]
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=20080303200917.GD19677@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=mchen@danger.com \
    --cc=mfouts@danger.com \
    --cc=msnyder@specifix.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