blob: c23876874fa1cd155db1ba5d5e4703d2998ff374 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
|
graphic: 0.811
device: 0.784
debug: 0.783
semantic: 0.718
boot: 0.683
mistranslation: 0.619
kernel: 0.601
socket: 0.598
user-level: 0.554
performance: 0.549
network: 0.497
risc-v: 0.481
x86: 0.464
architecture: 0.458
PID: 0.454
i386: 0.430
vnc: 0.421
register: 0.411
permissions: 0.404
ppc: 0.396
VMM: 0.361
arm: 0.355
KVM: 0.339
files: 0.319
hypervisor: 0.280
virtual: 0.274
peripherals: 0.230
TCG: 0.230
assembly: 0.182
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.
|
