From: "Luis Pureza" <pureza@student.dei.uc.pt>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Debugging QEMU
Date: Thu, 7 Feb 2008 19:00:24 +0000 [thread overview]
Message-ID: <3e1533500802071100r7d818cb5kb067bd5e26a9073a@mail.gmail.com> (raw)
[-- 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 --]
reply other threads:[~2008-02-07 19:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3e1533500802071100r7d818cb5kb067bd5e26a9073a@mail.gmail.com \
--to=pureza@student.dei.uc.pt \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).