qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vince Weaver <vince@csl.cornell.edu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] COMMIT e27b27b broke sparc32plus-linux-user
Date: Tue, 18 Aug 2009 11:23:26 -0400 (EDT)	[thread overview]
Message-ID: <20090817230737.I65734@stanley.csl.cornell.edu> (raw)

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.

Vince

             reply	other threads:[~2009-08-18 15:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-18 15:23 Vince Weaver [this message]
2009-08-18 15:40 ` [Qemu-devel] COMMIT e27b27b broke sparc32plus-linux-user Reimar Döffinger
2009-08-18 18:08 ` Blue Swirl

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=20090817230737.I65734@stanley.csl.cornell.edu \
    --to=vince@csl.cornell.edu \
    --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).