qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [Qemu-devel] Debugging QEMU
@ 2008-02-07 19:00 Luis Pureza
  0 siblings, 0 replies; only message in thread
From: Luis Pureza @ 2008-02-07 19:00 UTC (permalink / raw)
  To: qemu-devel

[-- Attachment #1: Type: text/plain, Size: 794 bytes --]

Hello,

I'm getting acquainted with QEMU's internals because I'll need to know them
very well for the next few months. I've reached a point where I want to
debug QEMU with gdb in order to better understand the code flux related to
some things that are still not clear after just looking at the code.

The thing is, debugging QEMU with GDB seems to be quite troublesome. GDB
keeps reporting the wrong source-code location when stepping through the
code and I'm unable to insert breakpoints at some of the most important
functions. I've tried to disable GCC optimizations, but the compilation
fails without -O2.

Is this my fault? How can I fix it?

Or, is this the expected behavior? In that case, which techniques do you use
to debug QEMU?

Thanks in advance,

Luís Pureza

[-- Attachment #2: Type: text/html, Size: 846 bytes --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2008-02-07 19:00 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-02-07 19:00 [Qemu-devel] Debugging QEMU Luis Pureza

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).