qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu & arm eabi (armel)
Date: Tue, 26 Sep 2006 23:30:41 +0100	[thread overview]
Message-ID: <200609262330.42113.paul@codesourcery.com> (raw)
In-Reply-To: <4519A630.8060300@palmsource.com>

On Tuesday 26 September 2006 23:14, K. Richard Pixley wrote:
> Ok, then I'm confused because I'm seeing dumps just trying to run a null
> program.  Unless there's NPTL setup stuff in crt0, I can't guess what
> might be going on yet.  This same null binary runs on a qemu-system with
> suitable rootfs & kernel.

The glibc startup code contains TLS initialisation that will fail on unpatched 
qemu. If you have applied the TLS patch there are a couple of other things 
that could cause problems:

- Make sure it's picking up the correct target shared libraries (or link your 
test application statically).
- Try configuring qemu with --static. The default (building qemu as a shared 
library) seems to cause strange problems on many systems.
- Make sure uname -r reports at least 2.6.16 (qemu can lie for you).

Paul

  reply	other threads:[~2006-09-26 22:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-26 21:26 [Qemu-devel] qemu & arm eabi (armel) K. Richard Pixley
2006-09-26 21:36 ` Rafael Espíndola
2006-09-26 21:36 ` Paul Brook
2006-09-26 22:14   ` K. Richard Pixley
2006-09-26 22:30     ` Paul Brook [this message]
2006-09-27 17:51       ` K. Richard Pixley
2006-09-27 18:00         ` Paul Brook
2006-09-27 18:27           ` K. Richard Pixley
2006-09-27 18:38             ` Paul Brook
2006-09-28  3:20               ` Re[2]: " Paul Sokolovsky
2006-09-28  3:39                 ` Paul Brook

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=200609262330.42113.paul@codesourcery.com \
    --to=paul@codesourcery.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).