Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: msnyder@redhat.com, gdb-patches@sourceware.org
Subject: Re: Save the length of inserted breakpoints
Date: Tue, 18 Apr 2006 08:59:00 -0000	[thread overview]
Message-ID: <uodyzxns5.fsf@gnu.org> (raw)
In-Reply-To: <20060417190808.GA22372@nevyn.them.org> (message from Daniel 	Jacobowitz on Mon, 17 Apr 2006 15:08:08 -0400)

> Date: Mon, 17 Apr 2006 15:08:08 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: msnyder@redhat.com, gdb-patches@sourceware.org
> 
> On the documentation front, I am quite mortified; I wrote this
> ChangeLog entry at least twice for earlier versions of the patch:
> 
>         * gdbint.texinfo (Watchpoints, Target Conditionals): Update insert
>         and remove breakpoint prototypes.
> 
> While they often use the underlying watchpoint registers, hardware
> breakpoints are breakpoints.  I've moved these to the Breakpoints
> section, and added some more bits there.  Eli, could you take a look
> at that?

Done, comments below.

>                                                @var{bp_tgt} is updated
> +to contain other information about the breakpoint on output:
> +@code{placed_address} may be updated if the breakpoint was placed at a
> +related address; @code{shadow_contents} is the real contents of the bytes
> +where the breakpoint has been inserted, if reading memory would return
> +the breakpoint instead of the underlying memory; @code{shadow_len} is the
> +length of memory cached in @code{shadow_contents}, if any; and
> +@code{placed_size} is optionally set and used by the target, if
> +it could differ from @code{shadow_len}.

This paragraph uses names of fields of the bp_target_info struct, but
it doesn't mention the name of the struct, and doesn't say that those
are its fields.  I suggest to modify the first sentence above like
this:

  Fields of @code{struct bp_target_info} pointed to by @var{bp_tgt}
  are updated to contain other information about the breakpoint on
  output: @code{@var{bp_tgt}->placed_address} may be updated if the
  breakpoint was placed ...

etc., you get the idea.  Alternatively, something like "the field
@code{placed_address} may be updated ..." is also okay.

> +@item i386_insert_hw_breakpoint (@var{bp_tgt})
> +@itemx i386_remove_hw_breakpoint (@var{bp_tgt})

This should mention the type of the struct:

 @item i386_insert_hw_breakpoint (struct bp_target_info *@var{bp_tgt})

Alternatively, mention the name of the struct in the text.

> +@item MEMORY_INSERT_BREAKPOINT (@var{bp_tgt})
> +@itemx MEMORY_REMOVE_BREAKPOINT (@var{bp_tgt})

Same here.

Otherwise, the patch is okay with me (including moving the description
of target_insert_hw_breakpoint and target_remove_hw_breakpoint.
Thanks!


  parent reply	other threads:[~2006-04-18  8:59 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-02 22:25 Daniel Jacobowitz
2006-03-02 23:13 ` Mark Kettenis
2006-03-02 23:19   ` Daniel Jacobowitz
2006-03-03  0:08     ` Mark Kettenis
2006-03-03  1:21       ` Daniel Jacobowitz
2006-03-03 13:51   ` Eli Zaretskii
2006-03-03 15:03     ` Daniel Jacobowitz
2006-03-03 17:56       ` Eli Zaretskii
2006-03-03 18:04         ` Daniel Jacobowitz
2006-03-03 22:00           ` Eli Zaretskii
2006-03-03 22:10             ` Daniel Jacobowitz
2006-03-03 22:35               ` Eli Zaretskii
2006-03-03 23:01                 ` Daniel Jacobowitz
2006-03-04 10:39                   ` Eli Zaretskii
2006-03-04 14:58                     ` Daniel Jacobowitz
2006-03-04 15:05                       ` Eli Zaretskii
2006-03-04 15:11                         ` Daniel Jacobowitz
2006-03-06 19:49                           ` Eli Zaretskii
2006-03-07  5:31               ` Michael Snyder
2006-03-04  0:35             ` Steven Johnson
2006-03-04 10:18               ` Daniel Jacobowitz
2006-04-11 21:46   ` Daniel Jacobowitz
2006-04-11 22:32     ` David S. Miller
2006-04-12  7:30     ` Eli Zaretskii
2006-04-12  9:44     ` Mark Kettenis
2006-04-12 12:57       ` Daniel Jacobowitz
2006-04-12 18:38         ` Mark Kettenis
2006-04-12 18:47           ` Daniel Jacobowitz
2006-04-13  8:12             ` Eli Zaretskii
2006-04-13 22:13               ` Mark Kettenis
2006-04-13 22:59                 ` Daniel Jacobowitz
2006-04-13 23:30                   ` Daniel Jacobowitz
2006-04-14  8:10                   ` Eli Zaretskii
2006-04-14  8:52                     ` David S. Miller
2006-04-14  8:04                 ` Eli Zaretskii
2006-04-14  8:51                   ` David S. Miller
2006-04-16 23:58                   ` Mark Kettenis
2006-04-17  7:07                     ` Eli Zaretskii
2006-04-13 21:57             ` Michael Snyder
2006-04-13 22:59               ` Daniel Jacobowitz
2006-04-16 23:53                 ` Mark Kettenis
2006-04-16 23:50               ` Mark Kettenis
2006-04-17  1:41                 ` Daniel Jacobowitz
2006-04-17 13:09                   ` Mark Kettenis
2006-04-17 13:37                     ` Daniel Jacobowitz
2006-04-17 13:50                       ` Mark Kettenis
2006-04-17 19:08                         ` Daniel Jacobowitz
2006-04-17 20:25                           ` Mark Kettenis
2006-04-17 21:50                             ` Daniel Jacobowitz
2006-04-18  8:59                           ` Eli Zaretskii [this message]
2006-04-18 19:21                             ` Daniel Jacobowitz
2006-04-19  7:40                               ` Eli Zaretskii

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=uodyzxns5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=msnyder@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