From: robert song <robertsong.stamp@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [DEBUG] how to use GDB to debug qemu?
Date: Thu, 29 Apr 2010 22:21:01 +0900 [thread overview]
Message-ID: <k2u662dcb9d1004290621v52f86e20z5b03f36d07f58bfb@mail.gmail.com> (raw)
In-Reply-To: <i2o662dcb9d1004270124m2d937cb4x1d5debbf66509709@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
> Then I just run "info cpus" as following.
> (QEMU) info cpus
>
> But now how can I get into the rountine of "info cpus" ?
> Of course, set trace point to the function can do the work, but if I
> don't know where the routine is, is there any way to step into the
> rountine?
>
Regarding to the question,
I found one tool named as tracef.
http://binary.nahi.to/hogetrace/#dl
It's in Japanese.
The tool can trace the functions called by qemu while recompling
qemu with exra options like -finstrument-functions.
It's just like strace and ltrace, but used to trace userland function.
Attach it to qemu, and the result can be got.
For exmaple:
[pid 26180] do_info_cpus() at 0x08056870
so do_info_cpus is used while you call "info cpus".
Currently tracef only supports x86 arch.
Hope this will help someone.
Best Regards,
robert
[-- Attachment #2: Type: text/html, Size: 1190 bytes --]
next prev parent reply other threads:[~2010-04-29 13:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 8:24 [Qemu-devel] [DEBUG] how to use GDB to debug qemu? robert song
2010-04-29 13:21 ` robert song [this message]
2010-04-29 13:22 ` [Qemu-devel] " robert song
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=k2u662dcb9d1004290621v52f86e20z5b03f36d07f58bfb@mail.gmail.com \
--to=robertsong.stamp@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).