From: davide.ferraretto@studenti.univr.it
To: qemu-devel@nongnu.org, wdongxu@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [Qemu-discuss] [Qemu-discussion] QEMU via GDB
Date: Mon, 24 Oct 2011 08:42:12 +0200 [thread overview]
Message-ID: <fc69f1426034.4ea524e4@studenti.univr.it> (raw)
In-Reply-To: <fc68daf05eb5.4ea523e1@studenti.univr.it>
[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]
It dosen't work. GDB returns the same error.
----- Original Message -----
From: davide.ferraretto@studenti.univr.it
Date: Monday, October 24, 2011 8:37
Subject: Re: [Qemu-discuss] [Qemu-discussion] QEMU via GDB
To: davide.ferraretto@studenti.univr.it
> It dosen't work. GDB return the same error.
>
> ----- Original Message -----
> From: davide.ferraretto@studenti.univr.it
> Date: Friday, October 21, 2011 16:18
> Subject: [Qemu-discuss] [Qemu-discussion] QEMU via GDB
> To: qemu-discuss@nongnu.org
>
> > 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.
[-- Attachment #2: Type: text/html, Size: 9195 bytes --]
parent reply other threads:[~2011-10-24 6:42 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <fc68daf05eb5.4ea523e1@studenti.univr.it>]
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=fc69f1426034.4ea524e4@studenti.univr.it \
--to=davide.ferraretto@studenti.univr.it \
--cc=qemu-devel@nongnu.org \
--cc=wdongxu@linux.vnet.ibm.com \
/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).