From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1Ae3KQ-00021H-UQ for qemu-devel@nongnu.org; Tue, 06 Jan 2004 21:21:50 -0500 Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1Ae3Jo-0001i9-0D for qemu-devel@nongnu.org; Tue, 06 Jan 2004 21:21:43 -0500 Received: from [199.232.41.8] (helo=mx20.gnu.org) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.24) id 1Ae3Jn-0001Ee-NJ for qemu-devel@nongnu.org; Tue, 06 Jan 2004 21:21:11 -0500 Received: from [128.187.28.163] (helo=mail.chem.byu.edu) by mx20.gnu.org with esmtp (Exim 4.24) id 1Ae2GM-0008Fx-Cf for qemu-devel@nongnu.org; Tue, 06 Jan 2004 20:13:34 -0500 Received: from isengard (isengard.chem.byu.edu [192.168.105.35]) by mail.chem.byu.edu (8.12.10/8.12.10) with ESMTP id i071B18Y025643 for ; Tue, 6 Jan 2004 18:11:01 -0700 Subject: Re: [Qemu-devel] segfault in current cvs From: Michael L Torrie In-Reply-To: <20040106202937.GP3483@suse.de> References: <20040106202937.GP3483@suse.de> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1073438011.4352.2.camel@isengard> Mime-Version: 1.0 Date: Tue, 06 Jan 2004 18:13:31 -0700 Reply-To: qemu-devel@nongnu.org List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Tue, 2004-01-06 at 13:29, Jens Axboe wrote: > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 16384 (LWP 15913)] > cpu_x86_exec (env1=0x0) at /home/axboe/qemu-cvs/cpu-exec.c:323 > 323 tb->cs_base = (unsigned long)cs_base; > (gdb) p tb > $1 = (TranslationBlock *) 0x0 > (gdb) p cs_base > $2 = (uint8_t *) 0x0 > (gdb) > This is the same segfault I get when running ordinary x86 linux binaries on my ppc yellowdog box. I hope we can find a solution to this problem. Michael > which looks odd, given the !tb check just a few lines up. I'm using: > > axboe@apu:/home/axboe $ gcc --version > gcc (GCC) 3.3.3 20031229 (prerelease) (Debian) -- Michael L Torrie