diff options
Diffstat (limited to 'results/classifier/zero-shot/108/other/581353')
| -rw-r--r-- | results/classifier/zero-shot/108/other/581353 | 31 |
1 files changed, 31 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/other/581353 b/results/classifier/zero-shot/108/other/581353 new file mode 100644 index 00000000..678b3306 --- /dev/null +++ b/results/classifier/zero-shot/108/other/581353 @@ -0,0 +1,31 @@ +graphic: 0.811 +device: 0.784 +debug: 0.783 +semantic: 0.718 +boot: 0.683 +socket: 0.598 +performance: 0.549 +network: 0.497 +other: 0.464 +PID: 0.454 +vnc: 0.421 +permissions: 0.404 +KVM: 0.339 +files: 0.319 + +qemu doesn't stop execution upon hitting a breakpoint + +Using Qemu 0.12.3 and gdb 7.1 on Ubuntu Lucid. + +I'm trying to debug some bootloader code. Using qemu -s -S to run the bootloader and gdb to connect to qemu, I set the breakpoint at 0x7c00. Then I type continue in gdb. The breakpoint is hit and gdb shows debug information. However qemu apparently continues to execute the code of the bootloader as the text is printed on the screen etc. + +Attached is the bootloader (no debug symbols as I'm debugging without them) + +Same thing happens to me, same versions as above.. I must turn to another app to accomplish my work while awaiting for a bug-fix, the code is perfectly executed but while gdb hits the breakpoints qemu goes on.. + +Ok this issue has been fixed in qemu 0.12.4. + +Just type 'qemu --version' to see what version you have, it is probably outdated. + +According to comment #3, this has been fixed, so let's change the bug status accordingly. + |