From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1GSLSE-0005xk-4e
	for qemu-devel@nongnu.org; Tue, 26 Sep 2006 18:31:06 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1GSLSD-0005x9-NO
	for qemu-devel@nongnu.org; Tue, 26 Sep 2006 18:31:05 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1GSLSD-0005wx-IY
	for qemu-devel@nongnu.org; Tue, 26 Sep 2006 18:31:05 -0400
Received: from [65.74.133.4] (helo=mail.codesourcery.com)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1GSLWw-0003Hf-FR
	for qemu-devel@nongnu.org; Tue, 26 Sep 2006 18:35:58 -0400
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] qemu & arm eabi (armel)
Date: Tue, 26 Sep 2006 23:30:41 +0100
References: <45199B1D.8040206@palmsource.com>
	<200609262236.39178.paul@codesourcery.com>
	<4519A630.8060300@palmsource.com>
In-Reply-To: <4519A630.8060300@palmsource.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200609262330.42113.paul@codesourcery.com>
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 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