From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GSdZa-0005ww-U6 for qemu-devel@nongnu.org; Wed, 27 Sep 2006 13:51:55 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GSdZa-0005w7-0p for qemu-devel@nongnu.org; Wed, 27 Sep 2006 13:51:54 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GSdZZ-0005w4-Tv for qemu-devel@nongnu.org; Wed, 27 Sep 2006 13:51:53 -0400 Received: from [12.7.175.14] (helo=mx2.palmsource.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GSdeT-0000cY-VG for qemu-devel@nongnu.org; Wed, 27 Sep 2006 13:56:58 -0400 Message-ID: <451ABA17.2000309@palmsource.com> Date: Wed, 27 Sep 2006 10:51:19 -0700 From: "K. Richard Pixley" MIME-Version: 1.0 Subject: Re: [Qemu-devel] qemu & arm eabi (armel) References: <45199B1D.8040206@palmsource.com> <200609262236.39178.paul@codesourcery.com> <4519A630.8060300@palmsource.com> <200609262330.42113.paul@codesourcery.com> In-Reply-To: <200609262330.42113.paul@codesourcery.com> Content-Type: multipart/alternative; boundary="------------030207020106010206020706" Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paul Brook Cc: qemu-devel@nongnu.org This is a multi-part message in MIME format. --------------030207020106010206020706 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Paul Brook wrote: > 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). > Done. > - Try configuring qemu with --static. The default (building qemu as a shared > library) seems to cause strange problems on many systems. > Done. > - Make sure uname -r reports at least 2.6.16 (qemu can lie for you). > Ah. Hm.. ubuntu-5 is currently: rpixley@svrpixleylnx> uname -a Linux svrpixleylnx 2.6.12-10-686-smp #1 SMP Tue Jul 18 23:03:01 UTC 2006 i686 GNU/Linux Do you know why 2.6.16 would be required? (I'll see if I can't find/build a 2.6.16 system on which to try it today.) --rich --------------030207020106010206020706 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Paul Brook wrote: 
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).
Done.
- Try configuring qemu with --static. The default (building qemu as a shared 
library) seems to cause strange problems on many systems.
Done.
- Make sure uname -r reports at least 2.6.16 (qemu can lie for you).
Ah.  Hm..  ubuntu-5 is currently:

rpixley@svrpixleylnx> uname -a
Linux svrpixleylnx 2.6.12-10-686-smp #1 SMP Tue Jul 18 23:03:01 UTC 2006 i686 GNU/Linux

Do you know why 2.6.16 would be required?  (I'll see if I can't find/build a 2.6.16 system on which to try it today.)

--rich
--------------030207020106010206020706--