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 1AcGSQ-0003Nj-LF for qemu-devel@nongnu.org; Thu, 01 Jan 2004 22:58:42 -0500 Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1AcGQ2-0002mU-B5 for qemu-devel@nongnu.org; Thu, 01 Jan 2004 22:56:46 -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 1AcGOQ-00011f-RG for qemu-devel@nongnu.org; Thu, 01 Jan 2004 22:54:34 -0500 Received: from [128.187.28.163] (helo=mail.chem.byu.edu) by mx20.gnu.org with esmtp (Exim 4.24) id 1AcFQG-0006P2-7x for qemu-devel@nongnu.org; Thu, 01 Jan 2004 21:52:24 -0500 Received: from [192.168.0.50] (ltbrpx28-port-44.dial.telus.net [161.184.29.66]) (authenticated bits=0) by mail.chem.byu.edu (8.12.10/8.12.10) with ESMTP id i022nt8Z009035 for ; Thu, 1 Jan 2004 19:49:56 -0700 From: Michael Torrie Content-Type: text/plain Message-Id: <1073011927.29451.5.camel@intrepid> Mime-Version: 1.0 Date: Thu, 01 Jan 2004 19:52:08 -0700 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Segmentation fault with 0.50 and 0.51 and fedora core ls Reply-To: qemu-devel@nongnu.org List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org I'm still having many problems using qemu to run all but the most basic static-ish x86 executables on my yellowdog ppc box. qemu just dies with a segmentation fault. I can run xterm, xeyes, ddd, and adobe acrobat reader, all from my x86 fedora core box (copying over the appropriate libraries for glibc, x11, etc). However, most other exes, even a simple exe like ls, fail with the segmentation fault. Since no one else is reporting this problem on the list, I think that perhaps it is an interaction between qemu and the ntpl-threaded glibc 2.3.3 that fedora core ships with. To replicate the problem, copy over ls and any dependent libraries to the yellowdog 3.0.1 box. run ls with qemu 0.51. qemu will quit with a segmentation fault. Doing some simple debugging indicates that there is a null pointer that is dereferenced somewhere in the synthetic cpu code. See my other posts from last month for the exact place in the code; I don't have the capabilities to debug qemu until I return from vacation.