Re: [PATCHv4 0/2] Make thread_info executing and resumed state more consistent

[Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>]

Craig Blackmore <craig.blackmore@embecosm.com> writes:

> On 21/04/2022 17:45, Andrew Burgess via Gdb-patches wrote:
>> And I'm back on this patch again!
>>
>> I've rebased this onto current master and done some testing.  I
>> haven't found any regressions, but as I've said before, this change
>> touches every target, and my testing on anything other than GNU/Linux
>> (x86-64) is pretty thin, so I'm fully expecting this to introduce some
>> issues - these issues _should_ be limited to assertion failures when
>> threads are not in the expected states, I would hope there's no
>> crashes being introduced.
>>
>> There's been no significant changes since v3.  I have split out a
>> little bit of the debug printing code (the new #1 patch), but the
>> second patch is pretty much the same as v3.
>>
>> V3 was given a cautious OK, but I wanted to advertise this patch again
>> in case anyone wants to object before I merge this.
>
> Hi Andrew,
>
> Do you still intend to merge the second patch in this series?

I do intend to return to this work, but I have another patch that I need
to get finished first before I'll have any free time to look at this.

When I do go back to this work I'm tempted to start fresh.  I was always
a little unsure about all the changes to the new thread creation code
(setting the resumed/executing flags in new threads), and I'm hoping
that if I start fresh then I might be able to come up with something
that feels a little cleaner.

That said, I'd certainly be supportive if anyone wanted to take this
patch on and move it forward.

Thanks,
Andrew