From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Ina37-0001Vf-0l
	for qemu-devel@nongnu.org; Thu, 01 Nov 2007 09:25:29 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Ina32-0001U5-HD
	for qemu-devel@nongnu.org; Thu, 01 Nov 2007 09:25:28 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Ina32-0001Tv-74
	for qemu-devel@nongnu.org; Thu, 01 Nov 2007 09:25:24 -0400
Received: from rv-out-0910.google.com ([209.85.198.190])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <felipe.contreras@gmail.com>) id 1Ina2w-0002Qm-MZ
	for qemu-devel@nongnu.org; Thu, 01 Nov 2007 09:25:24 -0400
Received: by rv-out-0910.google.com with SMTP id g11so1489832rvb
	for <qemu-devel@nongnu.org>; Thu, 01 Nov 2007 06:24:37 -0700 (PDT)
Message-ID: <94a0d4530711010624y6a6efb31gda6d3998211af6df@mail.gmail.com>
Date: Thu, 1 Nov 2007 15:24:37 +0200
From: "Felipe Contreras" <felipe.contreras@gmail.com>
Subject: Re: [Qemu-devel] qemu-arm fails with newer libc
In-Reply-To: <20071029185125.6aa079c3@bluebox.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20071029185125.6aa079c3@bluebox.local>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

On 10/29/07, Hans J. Koch <hjk@linutronix.de> 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