From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I20F4-0006Pm-4W for qemu-devel@nongnu.org; Sat, 23 Jun 2007 03:41:10 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I20F2-0006Nr-Dy for qemu-devel@nongnu.org; Sat, 23 Jun 2007 03:41:09 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I20F2-0006Na-6C for qemu-devel@nongnu.org; Sat, 23 Jun 2007 03:41:08 -0400 Received: from static-71-162-243-5.phlapa.fios.verizon.net ([71.162.243.5] helo=grelber.thyrsus.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1I20F1-0000iu-9F for qemu-devel@nongnu.org; Sat, 23 Jun 2007 03:41:07 -0400 Received: from landley.net (localhost [127.0.0.1]) by grelber.thyrsus.com (Postfix) with ESMTP id C2D9973E37 for ; Sat, 23 Jun 2007 03:41:19 -0400 (EDT) From: Rob Landley Subject: Re: [Qemu-devel] qemu-i386 segfaults running "hello world". Date: Sat, 23 Jun 2007 03:41:19 -0400 References: <200706221715.16729.rob@landley.net> <200706221831.20531.rob@landley.net> In-Reply-To: <200706221831.20531.rob@landley.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706230341.19544.rob@landley.net> 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 Friday 22 June 2007 18:31:20 Rob Landley wrote: > Ok, it's a more fundamental problem: > > landley@triolith:/sys$ qemu-i386 > Segmentation fault (core dumped) > > Nothing to do with the program it's trying to run, it segfaults with no > arguments. > > Is anybody else seeing this? > > Rob So I'm vaguely suspecting that some of the dynamic linker magic this thing's doing is contributing to the screw up (or at least the complexity of debugging it), so I thought I'd statically link. If I ./configure --static the result doesn't build, it dies during linking. Is this expected? (Do I need to install .a versions of all the alsa and x11 libraries to make that work?) I realize releases are a bit out of fashion, but is there any way to go through cvs to track down which checkin broke this stuff? I can do it in git, mercurial, or subversion. But cvs isn't really set up for this sort of thing... Rob -- "One of my most productive days was throwing away 1000 lines of code." - Ken Thompson.