[PATCH v7 3/5] gdb/remote: do not delete a thread if it has a pending exit event

Pedro Alves palves@redhat.com
Wed May 13 14:20:29 GMT 2020


On 5/4/20 4:33 PM, Aktemur, Tankut Baris via Gdb-patches wrote:
> On Monday, May 4, 2020 4:43 PM, Pedro Alves wrote:
>> Tankut,
>>
>> I'm trying to get back to this, and I would like to apply the whole
>> series locally, but I'm afraid that I'm having trouble piecing the
>> series together.
>> Do you have a public branch where you have all the patches in the series
>> applied?  You could push it under users/ on sourceware.org for example.
>>
>> Thanks,
>> Pedro Alves
> 
> Hi Pedro,
> 
> It's available at
> https://github.com/barisaktemur/gdb/commits/thread-exit-in-stop-all-threads-v8

Thanks Tankut.  I've been playing with this.  I'm now convinced that the
approach to make sure that we don't delete the last thread is the best one.
I've been experimenting with it, and I think we're OK wrt the
TARGET_WAITKIND_NO_RESUMED code in infrun.c. I pointed at before.
I've poked at the multi-exit.exp testcase to make it spawn more than
two inferiors, to make sure we always hit the race window, even on slower
systems.  I'm now looking at multi-kill.exp.  I'll have something to
show soon.

Thanks,
Pedro Alves



More information about the Gdb-patches mailing list