> When reading or writing memory, gdb specifies a thread. If it turns out
>> that the thread disappeared, GDB picks a thread, any thread (the
>> assumption being that all address spaces are pretty much similar).
>>
>> Mind you, I've seen thread implementations that implemented per-thread
>> local data using VM.
>
>
> It does not mean that everybody else should suffer, it is time to fix
> this youthful indiscretion.
Humor me. So who is suffering?
All things embedded and I suppose it is a much bigger market/user group
than ***ix one.
Why are ``all things embedded'' suffering?