From: Aurelien Jarno <aurelien@aurel32.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] TCG/GCC breakage
Date: Wed, 11 Mar 2009 09:32:22 +0100 [thread overview]
Message-ID: <20090311083222.GA21685@volta.aurel32.net> (raw)
In-Reply-To: <5d6222a80903102040reef9775s8aaf9975e7594133@mail.gmail.com>
On Wed, Mar 11, 2009 at 12:40:20AM -0300, Glauber Costa wrote:
> I'm seeing a strange behaviour here using qemu-system-x86_64
> (kvm not even compiled in) on an i386 host
>
> I'm suspecting gcc is doing something nasty in here, but I'll open it
> up here to see if any
> of you have any suggestion.
>
> I get segfaults very early in execution, and after some investigation,
> I figured out that
> ebp register is corrupted. I can't determine where the corruption starts.
Does QEMU segfault, or processes in the guest? How to reproduce that?
Which QEMU version are you using? I am able to run a Debian Etch x86_64
guest without problem here.
> I then did rm x86-64-softmmu/op_helper.o; make CC=gcc34, so only this
> file get compiled
> by an older gcc, and it worked again.
Which versions of gcc did you tried? I am using gcc 4.3 here.
> So it seems to me gcc may be generating gibberish somewhere in
> helpers, but since
> this code is a bit fragile, it might well be some mistake on our part.
>
> Ideas on how to attack it ?
>
You may want to use the -d option to find the offending helper function.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2009-03-11 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 3:40 [Qemu-devel] TCG/GCC breakage Glauber Costa
2009-03-11 8:32 ` Aurelien Jarno [this message]
2009-03-11 10:34 ` Paul Bolle
2009-03-16 8:26 ` Aurelien Jarno
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=20090311083222.GA21685@volta.aurel32.net \
--to=aurelien@aurel32.net \
--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).