Re: fix gdbserver's infinite loop when something goes wrong, after something having gone wrong...

[Tom Tromey <tromey at redhat dot com>]

>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:

Pedro> Note I'm thinking of making gdbserver also use gdb's exception/cleanup
Pedro> mechanism at some point.

This would perhaps make moving gdb to C++ harder.  Of course, this would
carry more weight if I actually sent in the proposal for it, etc; but
even so I think it merits some consideration.

I have been hoping that the shared code between gdb and gdbserver would
not rely on exceptions but instead would be in a more "plain C" style.

I suppose it could be that there are two orthogonal issues - how the
shared low-level bits are written, and how the rest of gdbserver is
structured internally.  In this case, I have no objections.

Tom