On 10/29/07, Hans J. Koch <[EMAIL PROTECTED]> wrote: > 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?
I'm also interested in this but so far I've not been able to make it work. Perhaps this would help: http://lists.scratchbox.org/pipermail/scratchbox-devel/2007-October/000349.html Best regards. -- Felipe Contreras