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?
I know of two cases:
a) The threads have a 100% shared address space. Binding memory
accesses to a thread will make zero difference.
b) The threads do not have a 100% shared address space. Binding memory
accesses to a thread will at least make it better reflect GDB's view of
a threads address space.
Forcing model (b) on underlying environment (a) will force unnecessary
invalidations of memory cache and will pretty negatively affect
performance of a debugging session.
I don't believe that it is even possible to measure a cache effect when
profiling GDB's single step performance(1) --- other, far bigger, host
or host<->target things things will drown any cache effects.