* [Qemu-devel] How to debug QEMU with GDB??
@ 2007-06-06 12:43 xdutaotao
2007-06-07 8:54 ` Mulyadi Santosa
0 siblings, 1 reply; 2+ messages in thread
From: xdutaotao @ 2007-06-06 12:43 UTC (permalink / raw)
To: qemu-devel
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
Hi,
I want to debug QEMU, but unfortunately after I set breakpoint in someplace
of QEMU, then continue to run, GDB give me the message:
"Continuing.
Warning:
Cannot insert breakpoint 1.
Error accessing memory address 0x2dad0: IN/OUT ERROR."
So I have to ask some question here?
1) How to find bug in QEMU if GDB doesn't work with QEMU?
2) What did you do when you must test your code of QEMU?
Thank you!
[-- Attachment #2: Type: text/html, Size: 4913 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Qemu-devel] How to debug QEMU with GDB??
2007-06-06 12:43 [Qemu-devel] How to debug QEMU with GDB?? xdutaotao
@ 2007-06-07 8:54 ` Mulyadi Santosa
0 siblings, 0 replies; 2+ messages in thread
From: Mulyadi Santosa @ 2007-06-07 8:54 UTC (permalink / raw)
To: qemu-devel; +Cc: xdutaotao
Hi...
Probably, it doesn't help you much, but have you check Qemu user forum
(http://qemu-forum.ipi.fi/)? There, in pending patch section, you can
find a patch that makes Qemu more gdb-friendly.
Another point is, are you sure you are putting breakpoint in .text
segment? Also, it is possible that some memory address range is write
protected (via mprotect) so you can't write there.
Jasson Wessel is the man I know who works closely with qemu-gdb related
stuffs... try to ask him.
regards,
Mulyadi
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-06-07 8:44 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-06-06 12:43 [Qemu-devel] How to debug QEMU with GDB?? xdutaotao
2007-06-07 8:54 ` Mulyadi Santosa
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).