All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Mayer" <l_indien@magic.fr>
To: qemu-devel@nongnu.org
Cc: Atoosaah S <atoosaah@gmail.com>
Subject: Re: [Qemu-devel] Unable to Run Gprof Successfully on QEMU
Date: Fri, 12 Oct 2007 10:26:37 +0200	[thread overview]
Message-ID: <1192177597.9976.250.camel@rapid> (raw)
In-Reply-To: <c3578ab90710120100x5c0170casf41589aa2eb01a2d@mail.gmail.com>

On Fri, 2007-10-12 at 01:00 -0700, Atoosaah S wrote:
> I'd appreciate any input on how to run gprof successfully on qemu. I'm
> new to gprof and am probably missing some steps.  I successfully ran
> gprof on a sorting program available online, then I attempted to run
> gprof on qemu. 
> 
> Here are the steps I take:
> 
> I'm trying to run gprof on qemu, but am unsuccessful. my os is linux,
> my qemu version is 0.8.2. I configure qemu with the options "configure
> --prefix=/install_path --enable-gprof. Then I make and make install. I
> run qemu successfully using the options /install_path/qemu -hda
> diskimage.img -m 256 which results in the gmon.out file. My run of
> qemu involved starting the image (virtual linux OS), running a few
> simple commands and shutting the image down.
> 
> Finally, I run gprof /intsall_path/qemu gmon.out > result.txt which
> gives the error: gprof: file 'qemu' has no symbols'
> 
> Are there any other configuration options required? Should the image
> be run with differently?

You need a qemu executable with debugging symbols. Distributed versions
are usually stripped, which means the debug symbols are not present
anymore.
A way to get the debug symbol is to fetch the source and recompile it...

-- 
J. Mayer <l_indien@magic.fr>
Never organized

  reply	other threads:[~2007-10-12  8:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-12  8:00 [Qemu-devel] Unable to Run Gprof Successfully on QEMU Atoosaah S
2007-10-12  8:26 ` J. Mayer [this message]
2007-10-12 15:13   ` Atoosaah S
2007-10-12 15:47     ` Ben Taylor
2007-10-12 18:55       ` Atoosaah S

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=1192177597.9976.250.camel@rapid \
    --to=l_indien@magic.fr \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.