From: Michael Torrie <torriem@chem.byu.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Segmentation fault with 0.50 and 0.51 and fedora core ls
Date: Fri, 02 Jan 2004 15:19:31 -0700 [thread overview]
Message-ID: <1073081971.1277.8.camel@intrepid> (raw)
In-Reply-To: <1073049292.21563.5.camel@rapid>
On Fri, 2004-01-02 at 06:14, J. Mayer wrote:
> Well, you may rebuild qemu as a static binary on your yellowdog
> distribution. If it compiles without a problem, you'll win :-)
> It seems really more simple than trying to make two glibc available on
> your system...
What does this have to do with my problem of qemu segfaulting when I run
x86 binaries? qemu builds and runs just fine. So that's not the
problem. It already compiles. Making qemu static will not help my
problem with glibc (remember it's the x86 glibc that's causing the
problems, not the ppc version). This is a bug in how qemu interacts
with the x86 glibc (in the gnemul folder). Not saying that it's not
related to the ppc glibc; just that what you're telling me doesn't seem
to fit with my problem.
To recap, xeyes, xterm, ddd, acrobat reader all work under qemu. I
copied them straight off my fedora core box. on my ppc yellowdog box,
qemu can run them just fine. Even a simple hello world that I compiled
works. However most other binaries cause qemu to segfault with a null
pointer problem, caused most likely by an interaction between qemu and
the x86 glibc stored in the /usr/gnemul folder.
Michael
Michael
next prev parent reply other threads:[~2004-01-02 23:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 2:52 [Qemu-devel] Segmentation fault with 0.50 and 0.51 and fedora core ls Michael Torrie
2004-01-02 3:26 ` J. Mayer
2004-01-02 4:47 ` Michael Torrie
2004-01-02 13:14 ` J. Mayer
2004-01-02 22:19 ` Michael Torrie [this message]
2004-01-03 0:23 ` J. Mayer
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=1073081971.1277.8.camel@intrepid \
--to=torriem@chem.byu.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).