From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pedro Alves <pedro@codesourcery.com>,
gdb-patches@sourceware.org,
Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: Re: [PATCH] fix spurious FAIL in py-inferior.exp (x86-solaris)
Date: Mon, 07 Mar 2011 05:21:00 -0000 [thread overview]
Message-ID: <20110307050445.GA31964@host1.jankratochvil.net> (raw)
In-Reply-To: <20110307043923.GN30306@adacore.com>
On Mon, 07 Mar 2011 05:39:23 +0100, Joel Brobecker wrote:
> > 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?
I do not have a fix but there seems to me mistaken LWP<->PID, each thread gets
duplicated once as {PID, 0, ID} and once as {PID, ID, 0}.
(gdb) info threads
Id Target Id Frame
10 Thread 4 (LWP 4) start3 (arg=0x0) at threadit.c:9
9 Thread 3 (LWP 3) start2 (arg=0x0) at threadit.c:8
8 Thread 2 (LWP 2) start1 (arg=0x0) at threadit.c:7
* 7 Thread 5 (LWP 5) start4 (arg=0x0) at threadit.c:10
6 LWP 5 start4 (arg=0x0) at threadit.c:10
5 LWP 4 start3 (arg=0x0) at threadit.c:9
4 LWP 3 start2 (arg=0x0) at threadit.c:8
3 LWP 2 start1 (arg=0x0) at threadit.c:7
2 Thread 1 (LWP 1) 0xfef022f5 in __lwp_wait () from /lib/libc.so.1
1 LWP 1 0xfef022f5 in __lwp_wait () from /lib/libc.so.1
Regards,
Jan
next prev parent reply other threads:[~2011-03-07 5:05 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 [this message]
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
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=20110307050445.GA31964@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=pedro@codesourcery.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