Re: [testsuite patch]#2 Fix PR threads/19422 regression + Guile regression [Re: [PATCH+doc] Fix PR threads/19422 - show which thread caused stop]

[Pedro Alves <palves@redhat.com>]

On 01/22/2016 08:05 PM, Jan Kratochvil wrote:
> On Fri, 22 Jan 2016 19:37:31 +0100, Pedro Alves wrote:
>> On 01/22/2016 05:31 PM, Jan Kratochvil wrote:
>>> OK to check-in the fix for both of these problems?
>>
>> I think I'm confused -- the first hunk shows that it's
>> thread 1 that receives the signal; then why do we need
>> the "thread 1" command?
> 
> I have looked more at it now and there is a race.  The following outputs are
> from unpatched FSF GDB HEAD:

...

> 
> racy case #2:
> 
> (xgdb) PASS: gdb.gdb/selftest.exp: Set xgdb_prompt
> ^M
> Thread 1 "xgdb" received signal SIGINT, Interrupt.^M
> 0x00007ffff583bfdd in poll () from /lib64/libc.so.6^M
> (gdb) FAIL: gdb.gdb/selftest.exp: send ^C to child process
> signal SIGINT^M
> Continuing with signal SIGINT.^M
> ^C^M
> Thread 2 "xgdb" received signal SIGINT, Interrupt.^M
> [Switching to Thread 0x7ffff3b7f700 (LWP 13227)]^M

So you need to adjust your patch in the bit that matched
"Thread 1", right?

Thanks,
Pedro Alves