From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1Bt6Be-0007XS-LR for qemu-devel@nongnu.org; Fri, 06 Aug 2004 10:59:14 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1Bt6Bc-0007Ww-Ut for qemu-devel@nongnu.org; Fri, 06 Aug 2004 10:59:14 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1Bt6Bc-0007Wt-Sf for qemu-devel@nongnu.org; Fri, 06 Aug 2004 10:59:12 -0400 Received: from [213.146.154.40] (helo=pentafluge.infradead.org) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1Bt67l-0005uw-EQ for qemu-devel@nongnu.org; Fri, 06 Aug 2004 10:55:13 -0400 Received: from [213.86.99.236] (helo=[172.16.18.64]) by pentafluge.infradead.org with asmtp (Exim 4.33 #1 (Red Hat Linux)) id 1Bt67g-0003Lj-LJ for qemu-devel@nongnu.org; Fri, 06 Aug 2004 15:55:11 +0100 Subject: Re: [Qemu-devel] ARM in big endian mode? From: David Woodhouse In-Reply-To: <20040711234327.GA16750@xi.wantstofly.org> References: <20040703160324.GD8894@xi.wantstofly.org> <1088940620.840.1.camel@sherbert> <20040704115730.GA21047@xi.wantstofly.org> <1089587847.4217.10.camel@localhost.localdomain> <20040711234327.GA16750@xi.wantstofly.org> Content-Type: text/plain Message-Id: <1091804107.4383.4898.camel@hades.cambridge.redhat.com> Mime-Version: 1.0 Date: Fri, 06 Aug 2004 15:55:07 +0100 Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Mon, 2004-07-12 at 01:43 +0200, Lennert Buytenhek wrote: > On Mon, Jul 12, 2004 at 12:17:27AM +0100, David Woodhouse wrote: > > > > % ./qemu-arm ./x > > > qemu: uncaught target signal 11 (Segmentation fault) - exiting <...> > Just checked, and indeed, LE binaries segfault too. <...> > So it looks like it (might have) worked in the past but broke somewhere > between then and now. Are you using a newer glibc now than the one you were using before? -- dwmw2