From: Pedro Alves <pedro@codesourcery.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] fix spurious FAIL in py-inferior.exp (x86-solaris)
Date: Mon, 07 Mar 2011 11:02:00 -0000 [thread overview]
Message-ID: <201103071050.08867.pedro@codesourcery.com> (raw)
In-Reply-To: <201103070920.p279KhVO031798@glazunov.sibelius.xs4all.nl>
On Monday 07 March 2011 09:20:43, Mark Kettenis wrote:
> > Date: Mon, 7 Mar 2011 08:39:23 +0400
> > From: Joel Brobecker <brobecker@adacore.com>
> >
> > > On Friday 04 March 2011 12:18:01, Mark Kettenis wrote:
> > > > That's a bug in the Solaris thread support. So...
> > >
> > > It's by design. Consequence of the M:N support, IIRC.
> > > (I didn't design it!)
> >
> > So, are we OK with this patch?
>
> Not really. Solaris has not been using a M:N for quite some time now.
Up until v8. I thought we still supported that version.
> And I think GDB should present threads in a consistent way.
Indeed. It raises the question of what is a "thread" from
gdb's perspective. In my mind, it's the "currently
active/visible sceduling entity granularity". dbx has
separate commands to list threads and lwps. Maybe gdb should
too. Bonus points if that is implemented with a proper
model that works against remote targets too.
--
Pedro Alves
prev parent reply other threads:[~2011-03-07 10:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 11:31 Joel Brobecker
2011-03-04 12:18 ` Mark Kettenis
2011-03-04 12:27 ` Pedro Alves
2011-03-07 5:05 ` Joel Brobecker
2011-03-07 5:21 ` Jan Kratochvil
2011-03-07 10:52 ` Pedro Alves
2011-03-07 9:49 ` Mark Kettenis
2011-03-07 10:16 ` Joel Brobecker
2011-03-07 11:02 ` Pedro Alves [this message]
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=201103071050.08867.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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