From: Blue Swirl <blauwirbel@gmail.com>
To: Vince Weaver <vince@csl.cornell.edu>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] COMMIT e27b27b broke sparc32plus-linux-user
Date: Tue, 18 Aug 2009 21:08:41 +0300 [thread overview]
Message-ID: <f43fc5580908181108v39c2d3bbp8259454899ba3b6e@mail.gmail.com> (raw)
In-Reply-To: <20090817230737.I65734@stanley.csl.cornell.edu>
On Tue, Aug 18, 2009 at 6:23 PM, Vince Weaver<vince@csl.cornell.edu> wrote:
> Hello
>
> I'm not sure how this is possible, but somehow the commit
>
> [COMMIT e27b27b] Simplify 5ba6531956b9b6486560cbd13604c2238a3542dd
>
> broke sparc32plus-linux-user for me. All the binaries I try now segfault.
>
> A small binary that exhibits this can be found in the ll qemu test found
> here:
> http://www.deater.net/weave/vmwprod/asm/ll/qemu_tests.html
> but larger binaries also have issues.
>
> It is very strange, as I can't see how that particular commit should
> change anything sparc related.
Should be fixed in git, thanks for the report.
prev parent reply other threads:[~2009-08-18 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 15:23 [Qemu-devel] COMMIT e27b27b broke sparc32plus-linux-user Vince Weaver
2009-08-18 15:40 ` Reimar Döffinger
2009-08-18 18:08 ` Blue Swirl [this message]
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=f43fc5580908181108v39c2d3bbp8259454899ba3b6e@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=vince@csl.cornell.edu \
/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).