Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Cc: gdb-patches@sourceware.org
Subject: Re: PATCH : allow to set length of hw watchpoints (e.g. for Valgrind gdbserver)
Date: Sun, 15 May 2011 17:47:00 -0000	[thread overview]
Message-ID: <83vcxbeu07.fsf@gnu.org> (raw)
In-Reply-To: <CF98DC37D4504926980AE0DDE3FE336F@soleil>

> From: "Philippe Waroquiers" <philippe.waroquiers@skynet.be>
> Date: Sun, 15 May 2011 19:38:44 +0200
> 
> With the last svn Valgrind, and this patch, the following
> watchpoint will be handled at a reasonable (i.e. "valgrind")
> speed:
> In the program being debugged:
>   char s[1000];
> 
> in gdb:
>   awatch s
> 
> as the hardware watchpoint will be accepted by the valgrind
> gdbserver, and implemented using Valgrind validity bits
> mechanism.

If this is accepted, I think this is NEWS worthy.

A few comments to the documentation part:

> + @item set remote hardware-watchpoint-length-limit @var{limit}
> + Restrict @value{GDBN} to using @var{limit} for the maximum length of
> + remote hardware watchpoints.  A limit of -1, the default, is treated
> + as unlimited.

I think we should tell explicitly that the limit is in bytes.  (Btw,
why the corresponding data types are `int' and not `ssize_t'?)

Also, I think we also document the "show" counterpart of each "set"
command.

Thanks.


  reply	other threads:[~2011-05-15 17:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-15 17:39 Philippe Waroquiers
2011-05-15 17:47 ` Eli Zaretskii [this message]
2011-05-15 20:12   ` Philippe Waroquiers
2011-05-15 20:30     ` Eli Zaretskii
2011-05-15 20:43       ` Philippe Waroquiers

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=83vcxbeu07.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=philippe.waroquiers@skynet.be \
    /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