From: Daniel Jacobowitz <drow@false.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] setting MIPS gdb breakpoints have wrong offsets
Date: Sun, 11 Jun 2006 20:43:27 -0400 [thread overview]
Message-ID: <20060612004327.GA14441@nevyn.them.org> (raw)
In-Reply-To: <448C8393.8060802@mail.berlios.de>
On Sun, Jun 11, 2006 at 10:56:51PM +0200, Stefan Weil wrote:
> 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.
This means that GDB has (mistakenly) decided that the first assembly
instruction in the function is part of a standard function prologue;
feel free to report a GDB bug.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-06-12 0:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-11 13:58 [Qemu-devel] setting MIPS gdb breakpoints have wrong offsets Dirk Behme
2006-06-11 20:56 ` Stefan Weil
2006-06-12 0:43 ` Daniel Jacobowitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060612004327.GA14441@nevyn.them.org \
--to=drow@false.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).