From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: strange crash on FreeBSD-current/amd64 (pointer truncation?)
Date: Sun, 4 Feb 2007 13:38:20 +0000 [thread overview]
Message-ID: <200702041338.20631.paul@codesourcery.com> (raw)
In-Reply-To: <19908A7B-B3B2-11DB-A6D1-003065C7D858@mandriva.com>
On Saturday 03 February 2007 18:12, Gwenole Beauchesne wrote:
> Hi,
>
> > Hmm. All I can say is the upper half of rbx (which holds T0) gets
> > spilled on FreeBSD-current/amd64 hosts unless saving and restoring
> > the full 64 bit of it...
>
> That's also what I got with VirtualBox on x86_64. Here is an update to
> the patch I posted yesterday and that applies to current QEMU CVS
> instead.
I rewrote it a bit and applied to CVS.
Paul
next prev parent reply other threads:[~2007-02-04 13:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 20:00 [Qemu-devel] strange crash on FreeBSD-current/amd64 (pointer truncation?) Juergen Lock
2007-02-01 20:00 ` [Qemu-devel] " Juergen Lock
2007-02-02 4:02 ` Thiemo Seufer
2007-02-02 21:45 ` Juergen Lock
2007-02-02 22:24 ` Thiemo Seufer
2007-02-03 1:43 ` Juergen Lock
2007-02-03 18:12 ` Gwenole Beauchesne
2007-02-04 13:38 ` Paul Brook [this message]
2007-02-02 22:27 ` andrzej zaborowski
2007-02-02 22:40 ` Paul Brook
2007-02-02 22:57 ` andrzej zaborowski
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=200702041338.20631.paul@codesourcery.com \
--to=paul@codesourcery.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).