From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DDQ8h-0000Ub-Kr for qemu-devel@nongnu.org; Mon, 21 Mar 2005 11:52:27 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DDQ8d-0000RX-17 for qemu-devel@nongnu.org; Mon, 21 Mar 2005 11:52:24 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DDQ8c-0000Qz-Nd for qemu-devel@nongnu.org; Mon, 21 Mar 2005 11:52:22 -0500 Received: from [195.135.220.2] (helo=Cantor.suse.de) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1DDPst-0008ER-14 for qemu-devel@nongnu.org; Mon, 21 Mar 2005 11:36:07 -0500 Received: from hermes.suse.de (hermes-ext.suse.de [195.135.221.8]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by Cantor.suse.de (Postfix) with ESMTP id C5FCC15F5138 for ; Mon, 21 Mar 2005 17:36:05 +0100 (CET) From: Ulrich Hecht Subject: Re: [Qemu-devel] S390 Status Date: Mon, 21 Mar 2005 17:36:04 +0100 References: <423E5D24.8010905@win4lin.com> <200503211559.35485.uli@suse.de> <423EF1B3.70105@win4lin.com> In-Reply-To: <423EF1B3.70105@win4lin.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200503211736.05060.uli@suse.de> 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 Hi! On Monday 21 March 2005 17:09, Jim Provan wrote: > Do you do your development on a real S390 or under Hercules ? The > reason that I ask is that I have an S390 available and would be > willing to put it on the net. I would give you all the time on it that > you need to be able to test out new patches for the S390. That would > go for any developers on this list as well that need S390 time. We're well-equipped with Mainframe machinery, but I don't have enough of a clue to be able to fix the problem, although I have the feeling that it can't be that big. It seems memory is being overwritten: (gdb) run Starting program: /abuild/uli/qemu/arm-user/qemu-arm /tmp/ldconfig-arm [Thread debugging using libthread_db enabled] [New Thread 1075738304 (LWP 4173)] program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1075738304 (LWP 4173)] cpu_arm_exec (env1=) at exec-all.h:229 229 if (tb->pc == pc && tb->cs_base == cs_base && tb->flags == flags) (gdb) info registers r0 0x0 0 r1 0x0 0 r2 0xc00a0e1 201367777 r3 0xbf2c 48940 r4 0x1bbdc 113628 r5 0x0 0 r6 0xbf2c 48940 r7 0x600aed69 1611328873 r8 0x40267338 1076261688 r9 0x7ffff2f4 2147480308 r10 0x611320d8 1628643544 r11 0x7fffef18 2147479320 r12 0x0 0 r13 0xe092efdc -527241252 r14 0xe00152d2 -536784174 r15 0x7fffeeb8 2147479224 pc 0x60015184 0x60015184 cc 0x2 2 (gdb) disassemble 0x60015184 [...] 0x60015184 : l %r1,0(%r2) So it apparently tries to read from address (%r2), which is 0x0c00a0e1, which is not a valid pointer, but looks very much like a little-endian ARM instruction to me. Unfortunately, my limited knowledge of 390 assembler does not allow me to track this down any further. CU Uli