From: Atoosah <atoosaah@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Using GDB with Qemu : No Symbol Table?
Date: Mon, 7 Jul 2008 17:42:36 -0700 [thread overview]
Message-ID: <c3578ab90807071742m5baa687cm4fd3c08ede852cdc@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]
Hi
Thank you for your help, but I think my question was misunderstood.
Debugging the kernel is not my goal. Instead, I want to debug qemu itself.
i.e. I want to be able to add watchpoints/breakpoints to qemu source code.
How do I compile Qemu to enable the symbol table?
My difficulty is that I need to be able to make install my_qemu (i.e. the
installed qemu version). Correct me if I'm wrong, but the -s -S options are
necessary if the goal is debugging the kernel. Is there a patch available,
such as the one provided in
http://www.h7.dion.ne.jp/~qemu-win/DebuggingTips-en.html/ (which seems to be
a rather old link)?
Thanks again.
On Wed, Jun 25, 2008 at 11:41 PM, Atoosah <atoosaah@gmail.com> wrote:
> $gdb vmlinux
> (gdb) target remote localhost:1234
> Remote debuggin using localhost:1234
> 0x0000fff0 in ?? ()
> (gdb) break main
> No symbol table is loaded. Use the "file" command.
> (gdb) c
> Continuing.
try to compile your kernel with CONFIG_DEBUG_INFO=y and
CONFIG_FRAME_POINTER=y. Both will enable gdb to easily resolve symbol
names into addresses and tracking down function call chain in stack
frame.
regards,
Mulyadi.
[-- Attachment #2: Type: text/html, Size: 1391 bytes --]
next reply other threads:[~2008-07-08 0:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 0:42 Atoosah [this message]
2008-07-08 14:34 ` [Qemu-devel] Using GDB with Qemu : No Symbol Table? Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2008-06-25 16:41 Atoosah
2008-06-26 2:16 ` Mulyadi Santosa
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=c3578ab90807071742m5baa687cm4fd3c08ede852cdc@mail.gmail.com \
--to=atoosaah@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).