A note about a GDB BoF topic - libgdbserver

Hi,

On the GDB BoF @ LPC this week [1], we discussed the possibility
of splitting gdbserver's core bits into a library so that
other projects like valgrind, embedded stubs, simulators, 
etc. could reuse it.

Licensing issues aside, the trouble as always is, who is
going to do the work, is there someone motivated to do it?

One thought that crossed my mind afterwards is a desire to
change how GDB supports the sim.  Instead of gdb's sim support
being implemented by gdb linking with libsim.a, it would be
better if we made the sim a separate gdbserver-like program that 
communicates with GDB via the remote protocol.  That would allow
for example connecting to multiple simulators at the same time,
even different simulators of different architectures at the
same time.

That seems like a good excuse to move in the libgdbserver
direction, and it doesn't even require thinking about
licensing.

Of course, another option would be to make gdbserver itself
link with libsim.a -- make the sim another gdbserver backend.
But that doesn't sound as cool.  ;-)

[1] https://www.youtube.com/watch?v=mMwC0QenvcA