From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LGXHc-00088F-T5 for qemu-devel@nongnu.org; Sat, 27 Dec 2008 06:24:40 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LGXHc-000883-0p for qemu-devel@nongnu.org; Sat, 27 Dec 2008 06:24:40 -0500 Received: from [199.232.76.173] (port=42407 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LGXHb-000880-KA for qemu-devel@nongnu.org; Sat, 27 Dec 2008 06:24:39 -0500 Received: from rv-out-0708.google.com ([209.85.198.246]:47624) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LGXHb-0004ji-68 for qemu-devel@nongnu.org; Sat, 27 Dec 2008 06:24:39 -0500 Received: by rv-out-0708.google.com with SMTP id f25so3660017rvb.22 for ; Sat, 27 Dec 2008 03:24:37 -0800 (PST) Message-ID: Date: Sat, 27 Dec 2008 12:24:37 +0100 From: "andrzej zaborowski" Subject: Re: [Qemu-devel] qemu-mips strange jump !!! In-Reply-To: <761ea48b0812270024t684c6258m3e6b1d46ef739833@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200812240123.mBO1N2NJ029937@fedora.exit.it> <49552429.5050808@exit.it> <761ea48b0812270024t684c6258m3e6b1d46ef739833@mail.gmail.com> 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 2008/12/27 Laurent Desnogues : > On Fri, Dec 26, 2008 at 7:36 PM, Alessandro Montano wrote: >> This is my first post, so sorry for any error ... >> I'm developing a DVB-S emulator based on qemu-mips. >> I'm adding all the device, once a time, but I notice a strange problem that >> crashes my emulator. >> >> It seems to do bad jumps! >> >> In brief ... I run this command >> *./bin/-qemu-system-mips -L . mips_bios.bin -d int,exec,op,in_asm >> *and it genereates this log >> >> IN: >> 0x80071fc4: lui at,0x8007 >> 0x80071fc8: lw a1,0xC094(at) >> 0x80071fcc: lui a0,0x8007 >> 0x80071fd0: addiu a0,a0,0xD060 >> 0x80071fd4: jal 0x8006d76c <- this is the right address >> 0x80071fd8: nop > [...] >> IN: >> 0x8006d968: andi t9,t9,0xdf <- but this is a wrong jump !!! >> 0x8006d96c: j 0x8006d90c >> 0x8006d970: ori t9,t9,0x20 > > You can't rely on logs to see the flow of a program. Not with "in_asm" alone, but "exec" should show the flow of execution, except DEBUG_EXEC is undefined by default. Maybe this should generate a runtime warning. Cheers