qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christian Wiese <developlists@gmx.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] BeOS/Zeta eats 100% cpu time
Date: Sun, 03 Oct 2004 20:57:01 +0200	[thread overview]
Message-ID: <41604B7D.2060201@gmx.de> (raw)
In-Reply-To: <200410012324.43055.paul@codesourcery.com>

Paul Brook wrote:

>Don't profile op.c. It's fairly sensitive to compiler options, and isn't 
>directly linked into qemu anyway. I ran into similar problems when building a 
>debuggable qemu.
>  
>
Ok, I now configure with --enable-gprof and it compiled fine. But as it 
looks like gprof writes it prof.out file when the executable close I 
have a new problem. BeOS do not "close" qEmu so that I have to kill the 
running process (with the "x" in the titlebar) and no file is writen. So 
does someone now a way to exit qEmu in a "normal" way, so that gprof 
will write it´s values into a file?

Greetings,
 Chris

  parent reply	other threads:[~2004-10-03 19:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-30 13:32 [Qemu-devel] BeOS/Zeta eats 100% cpu time Christian Wiese
2004-09-30 15:36 ` André Braga
2004-09-30 15:53   ` Christian Wiese
2004-09-30 17:07     ` André Braga
2004-09-30 17:27       ` Christian Wiese
2004-09-30 18:38         ` André Braga
2004-09-30 21:22           ` Andreas Bollhalder
2004-10-01  8:14           ` Christian Wiese
2004-10-01 16:24             ` André Braga
2004-10-01 21:06             ` Christian Wiese
2004-10-01 22:24               ` Paul Brook
2004-10-02  3:45                 ` Johannes Schindelin
2004-10-03 18:57                 ` Christian Wiese [this message]
2004-10-04  6:41                   ` Johannes Schindelin
2004-10-04  8:09                     ` Christian Wiese

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=41604B7D.2060201@gmx.de \
    --to=developlists@gmx.de \
    --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).