On Tue, Mar 22, 2011 at 11:02:09AM +0100, Jan Kiszka wrote:
> When the VM goes into stop state while there is a gdb frontend attached,
> it makes sense to inform gdb about this fact and at least a bit about
> the stop reason. Basically, all stops are interesting except for the
> temporary VMSTOP_SA
When the VM goes into stop state while there is a gdb frontend attached,
it makes sense to inform gdb about this fact and at least a bit about
the stop reason. Basically, all stops are interesting except for the
temporary VMSTOP_SAVE/LOADVM.
The patch maps the relevant VMSTOP reasons on unique and
