> * How I can see it myself? > > Almost real-world example: > > $ qemu -hda /path/to/linux-0.2.img -s # [1] > # wait at least until kernel is loaded > $ gdb # we'll mimic some Qt Creator actions here
Sorry, obviously here should be this instead: $ gdb -i mi > # normally we would provide target image, > # but it's not important to show the problem > set target-async on > target remote :1234 > # vm is interrupted now, try writing something in its win > -exec-continue > # vm is running now, your input shows > -exec-interrupt > # nothing happens, writing in vm still works, but it > # SHOULD NOT // apply patch to fix it > > You can even recompile qemu with uncommented DEBUG_GDB define in > gdbstub.c to see that appropriate packet is not sent with > -exec-interrupt. > > [1] http://wiki.qemu.org/download/linux-0.2.img.bz2 Regards. -- Przemysław 'Przemoc' Pawełczyk http://przemoc.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
