1 files changed, 38 insertions, 0 deletions
diff --git a/results/scraper/launchpad-without-comments/526653 b/results/scraper/launchpad-without-comments/526653
new file mode 100644
index 000000000..ecbe5898a
--- /dev/null
+++ b/results/scraper/launchpad-without-comments/526653
@@ -0,0 +1,38 @@
+Breakpoint on Memory address fails with KVM
+
+Using QEMU version 0.12.50 under ubuntu Karmic x64
+
+To reproduce the error using a floppy with a bootloder:
+qemu-system-x86_64 -s -S -fda floppy.img -boot a -enable-kvm
+
+connect with gdb:
+(gdb) set arch i8086
+The target architecture is assumed to be i8086
+(gdb) target remote localhost:1234
+Remote debugging using localhost:1234
+0x0000fff0 in ?? ()
+(gdb) break *0x7c00
+Breakpoint 1 at 0x7c00
+(gdb) continue
+Continuing.
+
+The breakpoint is not hit.
+
+If you close qemu and start it without kvm support:
+
+qemu-system-x86_64 -s -S -fda floppy.img -boot a
+
+(gdb) set arch i8086
+The target architecture is assumed to be i8086
+(gdb) target remote localhost:1234
+Remote debugging using localhost:1234
+0x0000fff0 in ?? ()
+(gdb) break *0x7c00
+Breakpoint 1 at 0x7c00
+(gdb) continue
+Continuing.
+
+Breakpoint 1, 0x00007c00 in ?? ()
+(gdb) 
+
+The breakpoint is hit.  If you wait until after the bootloader has been loaded into memory, you can properly set breakpoints with or without kvm enabled.
\ No newline at end of file