From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FpQSf-0001D5-Ha for qemu-devel@nongnu.org; Sun, 11 Jun 2006 09:58:41 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FpQSc-0001Ai-US for qemu-devel@nongnu.org; Sun, 11 Jun 2006 09:58:41 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FpQSc-0001AP-Me for qemu-devel@nongnu.org; Sun, 11 Jun 2006 09:58:38 -0400 Received: from [64.233.182.188] (helo=nf-out-0910.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FpQb8-0001RK-1U for qemu-devel@nongnu.org; Sun, 11 Jun 2006 10:07:26 -0400 Received: by nf-out-0910.google.com with SMTP id o25so755039nfa for ; Sun, 11 Jun 2006 06:58:36 -0700 (PDT) Message-ID: <448C218D.7040802@gmail.com> Date: Sun, 11 Jun 2006 15:58:37 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit From: Dirk Behme Subject: [Qemu-devel] setting MIPS gdb breakpoints have wrong offsets 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, I just tried to debug some simple MIPS code using qemu-system-mipsel by setting some breakpoints. If I use gdb's break command with symbol names the breakpoints are set at offsets and therefore they are never hit. Please find an example below. I'd like to stop the program if I get an interrupt, everything looks okay. But break command sets breakpoint at 0xbfc00384 instead of 0xbfc00380. Is this a bug or feature? I use qemu-system-mipsel with some of the pending MIPS patches applied locally. If this is a bug, can anybody else reproduce this? Any idea? Best regards Dirk (gdb) info address exception Symbol "exception" is at 0xbfc00380. (gdb) list exception 158 .end cache_miss 159 160 .org 0x380 161 .ent exception 162 exception: 163 j exception_handler 164 nop 165 .end exception 166 167 /**************************************************** (gdb) x/2i 0xbfc00380 0xbfc00380 : b 0xbfc0046c 0xbfc00384 : nop (gdb) break exception Breakpoint 1 at 0xbfc00384: file crt0.S, line 163. (gdb)