Re: Fix watchthreads-reorder.exp fails in linux gdbserver

[Pedro Alves <pedro at codesourcery dot com>]

On Monday 15 March 2010 00:50:06, Joel Brobecker wrote:
> > I've applied the patch below, to address in linux gdbserver the problem
> > watchthreads-reorder.exp uncovers, similarly to how it was fixed
> > in linux-nat.c.
> 
> This is a bit off topic, and even maybe a dream-that-will-never-come-true,
> but I've been wondering about sharing the wait loop between GDB and gdbserver.

This topic comes up all the time.

> Sounds like a big job at the very least (in order to extract the code
> from GDB for the platform currently supported), but do you think that
> it's actually doable / worth the effort?

It's doable, and in fact, I've been keeping that in mind over
the months, in the direction the non-stop and multi-process
gdbserver support changes have taken.

But, as you guessed, it would take a lot more effort.

> It's just that we're (actually,
> mostly you!) are very regularly fixing the same problem twice; once
> in GDB, and then once in gdbserver. Given the complexity of this code
> on some platforms, it's a real shame.

I believe that at some point this will end up happening, and it
will be GDBserver's side that will prevail.  It used to be that
native gdb was much more featureful than gdbserver, but the balance
is now starting to tip to the other direction.

-- 
Pedro Alves