From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LY4gC-0007OZ-0B for qemu-devel@nongnu.org; Fri, 13 Feb 2009 15:30:32 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LY4gA-0007LI-AJ for qemu-devel@nongnu.org; Fri, 13 Feb 2009 15:30:31 -0500 Received: from [199.232.76.173] (port=41139 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LY4gA-0007LA-7M for qemu-devel@nongnu.org; Fri, 13 Feb 2009 15:30:30 -0500 Received: from mail-bw0-f205.google.com ([209.85.218.205]:60381) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LY4g9-0002i3-SE for qemu-devel@nongnu.org; Fri, 13 Feb 2009 15:30:30 -0500 Received: by bwz1 with SMTP id 1so2092558bwz.10 for ; Fri, 13 Feb 2009 12:30:27 -0800 (PST) MIME-Version: 1.0 Date: Fri, 13 Feb 2009 22:30:27 +0200 Message-ID: From: Blue Swirl Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] PPC debugging broken 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" It looks like debugging confuses PPC branch code generation. For example, I'm doing single stepping from GDB: IN: cmdline_prompt 0xfff158a0: b 0xfff15960 (Unconditional branch to 0xfff15960) OP: movi_i32 nip,$0xfff15960 (OK, branch) movi_i32 nip,$0xfff158a4 (WTF?) movi_i32 tmp0,$0x10002 movi_i64 tmp1,$raise_exception call tmp1,$0x0,$0,tmp0 exit_tb $0x0 (Execution continues on $nip + 4 instead of branch target) IN: cmdline_prompt 0xfff158a4: lis r9,-12 OP: movi_i32 r9,$0xfff40000 movi_i32 nip,$0xfff158a8 movi_i32 nip,$0xfff158a8 movi_i32 tmp0,$0x10002 movi_i64 tmp1,$raise_exception call tmp1,$0x0,$0,tmp0 exit_tb $0x0