qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Rudi Lippert <Rudi@LYRIKpage.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: no start on amd64 (was "Nothing happens")
Date: Sun, 31 Jul 2005 15:58:11 +0200	[thread overview]
Message-ID: <dcil3s$kmf$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.58.0507311512460.18017@wgmdd8.biozentrum.uni-wuerzburg.de

Thanks for your reply.
I only created the bt because someone said it might help.
configure output looks fairly good to me, but I don't know much about those
things.
Is there anything else that might help understanding the problem?
Btw: Qemu is not even taking up CPU.


Install prefix    /usr
BIOS directory    /usr/share/qemu
binary directory  /usr/bin
Manual directory  /usr/share/man
ELF interp prefix /usr/gnemul/qemu-%M
Source path       /var/tmp/portage/qemu-softmmu-0.7.1/work/qemu-0.7.1
C compiler        gcc
Host C compiler   gcc
make              make
host CPU          x86_64
host big endian   no
target list       i386-softmmu ppc-softmmu sparc-softmmu x86_64-softmmu
gprof enabled     no
static build      no
SDL support       yes
SDL static link   yes
mingw32 support   no
Adlib support     no
FMOD support      no
kqemu support     yes


Johannes Schindelin wrote:
> Hi,
> 
> actually it looks more like the program was compiled with
> "-fomit-frame-pointer". For that reason, you only get correct names (and
> EIPs) for library calls.
> 
> Since QEmu uses as many physical registers as it can get, it is sensible
> to omit the frame pointer, because it has no meaning anyway once you are
> in translated code.
> 
> However, in your case I think it is more an SDL problem. Are you sure that
> the video mode you are trying to set is supported on your system? Could
> also be some sort of XShm hickup.
> 
> Ciao,
> Dscho
> 
> --
> Viruses love Micros**t

  reply	other threads:[~2005-07-31 13:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-31 12:47 [Qemu-devel] no start on amd64 (was "Nothing happens") Rudi Lippert
2005-07-31 13:19 ` Johannes Schindelin
2005-07-31 13:58   ` Rudi Lippert [this message]
2005-07-31 14:19     ` [Qemu-devel] " Johannes Schindelin
2005-07-31 15:25       ` [Qemu-devel] " Rudi Lippert
2005-07-31 18:17         ` Ozan Türkyılmaz
2005-07-31 22:37         ` Johannes Schindelin
2005-08-01 11:09           ` J. Mayer
2005-07-31 23:18         ` Joshua Root
2005-07-31 13:22 ` [Qemu-devel] " Paul Brook
  -- strict thread matches above, loose matches on Subject: below --
2005-08-01 20:42 [Qemu-devel] Re: no start on amd64 (was: " Rudi Lippert
2005-08-01 21:02 ` Johannes Schindelin
2005-08-01 21:06 ` J. Mayer

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='dcil3s$kmf$1@sea.gmane.org' \
    --to=rudi@lyrikpage.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).