public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: frank.theinen@lancom.de
To: Shaun Jackman <sjackman@gmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: BDI2000 "Cannot insert breakpoint"
Date: Wed, 03 Aug 2005 09:58:00 -0000	[thread overview]
Message-ID: <OF3DB83BF1.A166C077-ONC1257052.0036C54A-C1257052.00367671@lancom.de> (raw)

Hi Shaun,

> I am using a BDI2000 over Ethernet with gdb 6.3.50.20050801-cvs for
> arm-elf. Occasionally, if I have a breakpoint set a continue or next
> command will fail with an "Error accessing memory address" error as
> below:
> 
> (gdb) n
> Warning:
> Cannot insert breakpoint 0.
> Error accessing memory address 0x2017fe0: Unknown error 4294967295.
> 
> Often clearing the breakpoints with 'd b' and resetting the breakpoint
> will fix things. Is this perhaps related to hardware/software
> breakpoints? Any idea why it's failing?

yes, probably. If you configured the BDI2000 to use hardware breakpoints, 
and you have two breakpoints set, this will happen, when GDB "nexts" a 
subroutine call. GDB usually does single stepping, and when it 
single-steps into a subroutine, it sets a (kind of) temporary breakpoint 
at the position the LR points to and "continues" to leave the subroutine.

You can verify this behaviour by capturing the serial GDB communication 
where you can see the failing breakpoint setting operation.

Regards, Frank

             reply	other threads:[~2005-08-03  9:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-03  9:58 frank.theinen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-03  1:12 Shaun Jackman

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=OF3DB83BF1.A166C077-ONC1257052.0036C54A-C1257052.00367671@lancom.de \
    --to=frank.theinen@lancom.de \
    --cc=gdb@sources.redhat.com \
    --cc=sjackman@gmail.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).