On 2011-04-10 16:41, Avi Kivity wrote:
> On 04/10/2011 05:23 PM, Jan Kiszka wrote:
>> On 2011-04-10 16:01, Avi Kivity wrote:
>> > On 04/08/2011 11:52 PM, Jan Kiszka wrote:
>> >> QEMU's gdbstub in KVM mode is simply not designed to account for
>> guests
>> >> swapping out code pages that contain
On 04/10/2011 05:23 PM, Jan Kiszka wrote:
On 2011-04-10 16:01, Avi Kivity wrote:
> On 04/08/2011 11:52 PM, Jan Kiszka wrote:
>> QEMU's gdbstub in KVM mode is simply not designed to account for guests
>> swapping out code pages that contain breakpoints. Due to the fact that
>> the Linux kernel
On 2011-04-10 16:01, Avi Kivity wrote:
> On 04/08/2011 11:52 PM, Jan Kiszka wrote:
>> QEMU's gdbstub in KVM mode is simply not designed to account for guests
>> swapping out code pages that contain breakpoints. Due to the fact that
>> the Linux kernel does not do these weird things to its own code,
On 04/08/2011 11:52 PM, Jan Kiszka wrote:
QEMU's gdbstub in KVM mode is simply not designed to account for guests
swapping out code pages that contain breakpoints. Due to the fact that
the Linux kernel does not do these weird things to its own code,
It actually happily patches its own code at c
On 2011-04-08 20:50, Craig Brozefsky wrote:
> First, thank you very much for your work on KVM/QEMU and in particular
> the GDB support. I have been a heavy user of it while implementing a
> programmable debugger that monitors/traces guest operating systems. I
> need more breakpoints than hardware
