From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FpWzj-0005vS-W8 for qemu-devel@nongnu.org; Sun, 11 Jun 2006 16:57:16 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FpWzf-0005s4-R0 for qemu-devel@nongnu.org; Sun, 11 Jun 2006 16:57:14 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FpWzf-0005rt-JS for qemu-devel@nongnu.org; Sun, 11 Jun 2006 16:57:11 -0400 Received: from [212.227.126.177] (helo=moutng.kundenserver.de) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FpX8E-0003DV-Rm for qemu-devel@nongnu.org; Sun, 11 Jun 2006 17:06:03 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) by flubber.weilnetz.de (Postfix) with ESMTP id 5D86EF2D86 for ; Sun, 11 Jun 2006 22:56:52 +0200 (CEST) Message-ID: <448C8393.8060802@mail.berlios.de> Date: Sun, 11 Jun 2006 22:56:51 +0200 From: Stefan Weil MIME-Version: 1.0 Subject: Re: [Qemu-devel] setting MIPS gdb breakpoints have wrong offsets References: <448C218D.7040802@gmail.com> In-Reply-To: <448C218D.7040802@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 Dirk, when I set a breakpoint to address 0x80000180 ("b *0x80000180"), this works as expected. So do breakpoints to symbolic addresses in the Linux kernel. "info breakpoints" shows address 0xffffffff80000180 for the first example. Maybe "b *0xbfc00380" works for your case. If it does, your mips-gdb is somehow strange. Regards Stefan Dirk Behme schrieb: > 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