[PATCH 3/N] remote follow fork and spurious child stops in non-stop mode
Pedro Alves
palves@redhat.com
Wed Jul 29 15:40:00 GMT 2015
On 07/29/2015 03:23 PM, Pedro Alves wrote:
> On 07/29/2015 02:38 PM, Pedro Alves wrote:
>
>> Ignore the "SIGTRAP" mention in "SEL: Found 2 SIGTRAP events",
>> it's "two events". And the one that was picked was a process
>> exit. But the tail end of linux_wait_1 isn't expecting that
>> can happen.
>>
>
> This seems to fix it (and ends up making the code a little
> more like linux-nat.c). I'm running it through the testsuite.
It passes cleanly.
And I confirmed that that test idea triggers the suspend count
assertion I suspected:
Child exited with status 0
/home/pedro/gdb/mygit/build/../src/gdb/gdbserver/linux-low.c:2619: A problem internal to GDBserver has been detected.
unsuspend_one_lwp: Assertion `lwp->suspended >= 0' failed.
[Inferior 1 (process 32473) exited with code 01]
(gdb)
I'll convert that to a proper test.
Thanks,
Pedro Alves
More information about the Gdb-patches
mailing list