From: Davide <outshell88@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] QEMU via GDB
Date: Fri, 21 Oct 2011 08:29:31 +0200 [thread overview]
Message-ID: <4EA1114B.5000303@gmail.com> (raw)
Dear all,
I am trying to debug QEMU via GDB.
I configured and compiled QEMU with debugging flags, i.e.,
# CFLAGS="-g3 -O0" ./configure --disable-gfx-check
and run gdb:
# gdb ./i386-linux-user/qemu-i386
(gdb) break main
(gdb) run
Starting program: /home/test/femu/i386-linux-user/qemu-i386
Failed to read a valid object file image from memory.
Warning:
Cannot insert breakpoint 1.
Error accessing memory address 0x2f7df: Input/output error.
Is there any extra flag to be specified with the GDB for QEMU debugging?
I am wondering if the QEMU virtual machine creates any problem to the
GDB virtual machine.
Thanks.
G.
next reply other threads:[~2011-10-21 6:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 6:29 Davide [this message]
2011-10-21 7:14 ` [Qemu-devel] QEMU via GDB Robert Wang
-- strict thread matches above, loose matches on Subject: below --
2011-10-21 7:04 davide.ferraretto
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=4EA1114B.5000303@gmail.com \
--to=outshell88@gmail.com \
--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).