From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Segfaulting on Solaris10u5/sparc?
Date: Sun, 25 May 2008 09:46:39 +0300 [thread overview]
Message-ID: <f43fc5580805242346u706deadbx65f520d33320f99c@mail.gmail.com> (raw)
In-Reply-To: <db7b3ca90805241908j1f7e70eaj296b8dd0d3c637d6@mail.gmail.com>
On 5/25/08, Jonathan Kalbfeld <jonathan.kalbfeld@gmail.com> wrote:
> I built my QEMU using all the same tools I have been using for months,
> i.e., blastwave GCC, etc.
>
> Consistently QEMU seems to segmentation fault for the last two weeks.
> I have been using the CVS head.
CVS? I hope you mean SVN.
> Is there something I should know about the sparc edition?
Sparc host support is being converted to TCG, but the process is still
unfinished. Handcrafted Sparc32/Sparc64 helloworld programs run on
Sparc32plus/Sparc64 host without crashing.
prev parent reply other threads:[~2008-05-25 6:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-25 2:08 [Qemu-devel] Segfaulting on Solaris10u5/sparc? Jonathan Kalbfeld
2008-05-25 6:46 ` 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=f43fc5580805242346u706deadbx65f520d33320f99c@mail.gmail.com \
--to=blauwirbel@gmail.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).