This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] fix spurious FAIL in py-inferior.exp (x86-solaris)
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