Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: [RFA/doc] TARGET_ADJUST_BREAKPOINT_ADDRESS - patch 2 of 4
Date: Sat, 04 Oct 2003 03:08:00 -0000	[thread overview]
Message-ID: <1031004030829.ZM24969@localhost.localdomain> (raw)

[This is a repost of the patch I posted earlier, but with the correct
subject line.]

This is patch 2, the documentation patch for my current set of
TARGET_ADJUST_BREAKPOINT_ADDRESS patch submissions.

For an overview of the past history regarding this patch, see:

    http://sources.redhat.com/ml/gdb-patches/2003-10/msg00070.html

Okay?

Kevin

	* gdbint.texinfo (TARGET_ADJUST_BREAKPOINT_ADDRESS): Document.

Index: doc/gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.172
diff -u -p -r1.172 gdbint.texinfo
--- doc/gdbint.texinfo	2 Oct 2003 20:28:31 -0000	1.172
+++ doc/gdbint.texinfo	3 Oct 2003 23:38:30 -0000
@@ -3052,6 +3052,22 @@ custom breakpoint insertion and removal 
 @code{BREAKPOINT_FROM_PC} needs to read the target's memory for some
 reason.
 
+@item TARGET_ADJUST_BREAKPOINT_ADDRESS (@var{address})
+@findex TARGET_ADJUST_BREAKPOINT_ADDRESS
+Given an address at which a breakpoint is desired, return a breakpoint
+address adjusted to account for architectural constraints on
+breakpoint placement.  This method is not needed by most targets.
+
+The FR-V target (see @file{frv-tdep.c}) requires this method.  The
+FR-V is a VLIW architecture whose VLIW instructions consist of a
+number of RISC-like subinstructions which execute in parallel.  This
+architecture requires that breakpoints only be placed on the first
+subinstruction of a VLIW (aggregate) instruction.
+
+Since the adjustment of a breakpoint may radically alter a user's
+expectation, @value{GDBN} prints a warning when an adjusted breakpoint
+is initially set and each time that that breakpoint is hit.
+
 @item DEPRECATED_CALL_DUMMY_WORDS
 @findex DEPRECATED_CALL_DUMMY_WORDS
 Pointer to an array of @code{LONGEST} words of data containing


             reply	other threads:[~2003-10-04  3:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-04  3:08 Kevin Buettner [this message]
2003-10-07 21:46 ` Eli Zaretskii
2003-10-13 23:47   ` Kevin Buettner
2003-10-14  5:53     ` Eli Zaretskii
2003-10-14 20:26       ` 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=1031004030829.ZM24969@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=eliz@elta.co.il \
    --cc=gdb-patches@sources.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