Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfc] Set a breakpoint's type before adjusting its address
Date: Sat, 28 Apr 2007 21:54:00 -0000	[thread overview]
Message-ID: <20070428214510.GA12239@caradoc.them.org> (raw)
In-Reply-To: <20070427151559.0394bfa0@ironwood.lan>

On Fri, Apr 27, 2007 at 03:15:59PM -0700, Kevin Buettner wrote:
> At the moment, running GDB on an FR-V target will generate lots of
> "reading through apparently deleted breakpoint" warnings.  This is due
> to the fact that (due to architectural constraints) FR-V needs to
> adjust breakpoint addresses.  When it does so, it reads through
> read_memory_nobpt(), triggering the warning due to the fact that the
> breakpoint's type hasn't been set yet.  The patch below moves the type
> assignment prior to the adjustment thus avoiding this situation.
> 
> Comments?
> 
> 	* breakpoint.c (set_raw_breakpoint): Set breakpoint type before
> 	attempting to adjust its address.

This happens because the breakpoint's location is already on the
location chain, right?  Alternatively, we could move that from the end
of allocate_bp_location to the end of set_raw_breakpoint, and avoid
the inconsistency.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-04-28 21:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-27 22:25 Kevin Buettner
2007-04-28 21:54 ` Daniel Jacobowitz [this message]
2007-05-03  0:15   ` Kevin Buettner
2007-05-03  2:38     ` Daniel Jacobowitz
2007-05-03 17:44       ` Kevin Buettner

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=20070428214510.GA12239@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@redhat.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