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 1AcICG-0004l3-8y for qemu-devel@nongnu.org; Fri, 02 Jan 2004 00:50:08 -0500 Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1AcIBi-0004UN-CU for qemu-devel@nongnu.org; Fri, 02 Jan 2004 00:50:05 -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 1AcIBh-0004SW-VT for qemu-devel@nongnu.org; Fri, 02 Jan 2004 00:49:33 -0500 Received: from [128.187.28.163] (helo=mail.chem.byu.edu) by mx20.gnu.org with esmtp (Exim 4.24) id 1AcHDW-0008Ol-B5 for qemu-devel@nongnu.org; Thu, 01 Jan 2004 23:47:22 -0500 Received: from [192.168.0.50] (ltbrpx28-port-1.dial.telus.net [161.184.29.23]) (authenticated bits=0) by mail.chem.byu.edu (8.12.10/8.12.10) with ESMTP id i024j08Z009380 for ; Thu, 1 Jan 2004 21:45:02 -0700 Subject: Re: [Qemu-devel] Segmentation fault with 0.50 and 0.51 and fedora core ls From: Michael Torrie In-Reply-To: <1073013983.7385.9.camel@rapid> References: <1073011927.29451.5.camel@intrepid> <1073013983.7385.9.camel@rapid> Content-Type: text/plain Message-Id: <1073018837.4731.58.camel@intrepid> Mime-Version: 1.0 Date: Thu, 01 Jan 2004 21:47:17 -0700 Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Thu, 2004-01-01 at 20:26, J. Mayer wrote: > You're right, this is the right explanation. > I've already seen this problem, but didn't solve it, with a recent > Debian using glibc 2.3... > The glibc 2.3 signal context structure isn't the same that the one used > in glibc 2.2. This makes qemu think that the emulated program is doing > invalid access while it should detect some valid write access to code > pages. > > I'm surprised that you were able to compile qemu with this glibc. When I > tried to use glibc 2.3 on PPC, qemu failed to compile, because the > structure field names also changed. Are your headers fully synchronised > with your libc ? qemu was compiled on my yellowdog ppc box, which doesn't use the nptl glibc-2.3.3. I think it's still glibc-2.3.1, without nptl. > I don't believe it's a thread-scheme problem, because qemu don't use > threads. Or it may be some other glibc definitions or structure padding > or alignment which aren't the same than in the regular glibc... I guess I'll have to try downloading a non-nptl x86 glibc and try that. But it would be nice to figure out how to get the nptl glibc working with qemu (even in non-nptl mode, since nptl would depend on the kernel support). Since many of the exe's I'd be wanting to run depend on GLIBC_2.3, I could compile a special version of glibc that doesn't use nptl. Would that work? Or are there still internal changes that would prohibit this right now? Michael > > Regards.