qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Hans J. Koch" <hjk@linutronix.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qemu-arm fails with newer libc
Date: Mon, 29 Oct 2007 18:51:25 +0100	[thread overview]
Message-ID: <20071029185125.6aa079c3@bluebox.local> (raw)

I'm trying to set up an environment where I can use a command like

qemu-arm -L /path/to/root-file-system my_program

I tried qemu from latest Debian unstable, and couldn't make it work. I
then downloaded the latest snapshot (qemu-snapshot-2007-10-29_05). I
used a recent version of the CodeSourcery toolchain.

As it is, qemu-arm fails with an error like this:

qemu: Unsupported syscall: 983045

which indicates missing TLS support. I found this patch:

http://www.freaknet.org/martin/QEMU/patch.qemu-0.8.2_nptl-pb147082-mg1

and managed to apply it to the current code. It solves the TLS problem,
but now fails with a different error:

qemu: unhandled CPU exception 0x8 - aborting
R00=421a5c14 R01=00000000 R02=421a5c08 R03=00000001
R04=4008ef88 R05=00000000 R06=00000000 R07=00000000
R08=00000000 R09=00000000 R10=400a5000 R11=00000000
R12=ffff0fff R13=4007f858 R14=420b4b3c R15=ffff0fa0
PSR=20000010 --C- A usr32
...(registers in between are all zero)...
qemu: uncaught target signal 6 (Aborted) - exiting

This is exactly the same behaviour as shown by the Debian version of
qemu. Maybe they applied the same patch...

The problem does not show up if I use libraries from an old (2 years)
Timesys toolchain, so it seems to be triggered by code found in recent
libc versions.

What can I do now? Is this a known problem? Any patches for that?

Thanks,
Hans

             reply	other threads:[~2007-10-29 17:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-29 17:51 Hans J. Koch [this message]
2007-11-01 13:24 ` [Qemu-devel] qemu-arm fails with newer libc Felipe Contreras
2007-11-05 12:26   ` Hans-Jürgen Koch

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=20071029185125.6aa079c3@bluebox.local \
    --to=hjk@linutronix.de \
    --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).