>>Of course, a simpler and less intrusive fix would be to simply
>>define PREPARE_TO_PROCEED as generic_prepare_to_proceed, and
>>remove lin_lwp_prepare_to_proceed.
Yes (well using set_gdbarch_prepare_to_proceed() :-). Hmm, things to do
for someone --- add a linux-tdep.c file?
I've got a linux-nat already in my local tree, might as well do a
linux-tdep... but then I'd need to hook this in to all the osabi stuff,
and I'd rather not add it as GNU/Linux-specific only to make it global
after we branch.
Are you saying we should do the less invasive fix as above? It won't
work unless I move the definition to the tm headers, since this affects
cross targets too. I'd rather see the default changed as I proposed,
if you're comfortable with it. Then after the branch we can look at
the other platforms which have their own custom version.
[I'm never quite clear what you mean when you answer a thread with "yes"
:)]
I agree with michael.