qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "J. Mayer" <l_indien@magic.fr>
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 04:26:23 +0100	[thread overview]
Message-ID: <1073013983.7385.9.camel@rapid> (raw)
In-Reply-To: <1073011927.29451.5.camel@intrepid>

On Fri, 2004-01-02 at 03:52, Michael Torrie wrote:
> I'm still having many problems using qemu to run all but the most basic
> static-ish x86 executables on my yellowdog ppc box.  qemu just dies with
> a segmentation fault.  I can run xterm, xeyes, ddd, and adobe acrobat
> reader, all from my x86 fedora core box (copying over the appropriate
> libraries for glibc, x11, etc).  However, most other exes, even a simple
> exe like ls, fail with the segmentation fault.  Since no one else is
> reporting this problem on the list, I think that perhaps it is an
> interaction between qemu and the ntpl-threaded glibc 2.3.3 that fedora
> core ships with.

You're right, this is the right explanation.
I've already seen this problem, but didn't solve it, with a recent
Debian using glibc 2.3...
The glibc 2.3 signal context structure isn't the same that the one used
in glibc 2.2. This makes qemu think that the emulated program is doing
invalid access while it should detect some valid write access to code
pages.

I'm surprised that you were able to compile qemu with this glibc. When I
tried to use glibc 2.3 on PPC, qemu failed to compile, because the
structure field names also changed. Are your headers fully synchronised
with your libc ?
I don't believe it's a thread-scheme problem, because qemu don't use
threads. Or it may be some other glibc definitions or structure padding
or alignment which aren't the same than in the regular glibc...

Regards.

-- 
J. Mayer <l_indien@magic.fr>
Never organized

  reply	other threads:[~2004-01-02  4:39 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 [this message]
2004-01-02  4:47   ` Michael Torrie
2004-01-02 13:14     ` J. Mayer
2004-01-02 22:19       ` Michael Torrie
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=1073013983.7385.9.camel@rapid \
    --to=l_indien@magic.fr \
    --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).