From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I23MF-00070y-3t for qemu-devel@nongnu.org; Sat, 23 Jun 2007 07:00:47 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I23ME-00070J-3N for qemu-devel@nongnu.org; Sat, 23 Jun 2007 07:00:46 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I23MD-00070D-Nm for qemu-devel@nongnu.org; Sat, 23 Jun 2007 07:00:45 -0400 Received: from brick.kernel.dk ([80.160.20.94] helo=kernel.dk) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1I23MD-0006cf-07 for qemu-devel@nongnu.org; Sat, 23 Jun 2007 07:00:45 -0400 Received: from nelson.home.kernel.dk (nelson.home.kernel.dk [192.168.0.33]) by kernel.dk (Postfix) with ESMTP id 2139325793E for ; Sat, 23 Jun 2007 13:00:39 +0200 (CEST) Date: Sat, 23 Jun 2007 13:00:03 +0200 From: Jens Axboe Subject: Re: [Qemu-devel] qemu-i386 segfaults running "hello world". Message-ID: <20070623110003.GP30033@kernel.dk> References: <200706221715.16729.rob@landley.net> <200706221831.20531.rob@landley.net> <200706230341.19544.rob@landley.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <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 Sat, Jun 23 2007, Rob Landley wrote: > 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... git clone git://git.kernel.dk/data/git/qemu.git and bisect on that then. It's a continued git import of the cvs repo, gets updated every night. -- Jens Axboe