Impossible to debug an OS with Bochs/Gdb and mouse capture ?

[VMo]

Hello to all !
I have the following problem which blocks my development.
I am working on Ubuntu with Gdb and Bochs+Gdb stub to run an experimental OS which uses the mouse.
I start Gdb and Bochs with mouse capture deactivated, connection is ok, continue on Gdb launches the exec, all inits sequences work.
Then when mouse input is required I switch Bochs to mouse capture mode by clicking Bochs menu bar, this brings Bochs window in front and Gdb window is behind. Mouse interrupts are correctly handled and the cursor moves. Until there everything is ok.

The problem arises when a breakpoint is reached or an exception occurs and Bochs stops after reporting to Gdb : it is then impossible to select and bring to front Gdb's windows because Bochs hogged the mouse input, but in the same time Bochs does not respond to mouse capture toggle because it is stopped waiting on Gdb. It also does not respond to keyboard input whatever ctrl sequence is given.
The situation is a complete blockage with impossibility to regain control on the graphic interface. This blockage seems to be only solved by ctrl-alt-fkeying to console and killing Gdb + Bochs to be back in control of the computer.

If there is no way around this problem, it means that debugging an OS using mouse input with Gdb stubbed Bochs and Gdb is simply impossible.

Or am I wrong somewhere ?

[stlw]

Hello,

Volker just merged fix for the problem to SVN *rev10779* for coming 2.5 release.
Can you please try latest Bochs SVN and see if the issue disappears?

Thanks
Stanislav