From: Yao Qi <yao@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: Re: ping: Re: PATCH : allow to set length of hw watchpoints (e.g. for Valgrind gdbserver)
Date: Fri, 27 May 2011 03:25:00 -0000 [thread overview]
Message-ID: <4DDF196F.5010202@codesourcery.com> (raw)
In-Reply-To: <CDA9C6B129F5458D9301BA5289052C97@soleil>
On 05/22/2011 06:20 AM, Philippe Waroquiers wrote:
I am not the people to approve or reject this patch.
>
> *** Changes since GDB 7.3
>
> + * GDB has two new commands: "set remote hardware-watchpoint-length-limit"
> + and "show remote hardware-watchpoint-length-limit". These allows to
> + set or show the maximum length limit (in bytes) of a remote
> + target hardware watchpoint.
> + + This allows e.g. to use "unlimited" hardware watchpoints with the
^ Looks there is a surplus '+'.
> + gdbserver integrated in Valgrind version >= 3.7.0. Such Valgrind
> + watchpoints are slower than real hardware watchpoints but are
> + significantly faster than gdb software watchpoints.
If I understand you correctly, this commands are only useful in
gdbserver+valgrind. If gdb is running in normal remote target, using
`set remote hardware-watchpoint-length-limit' will make GDB work
incorrectly.
Maybe, we need a new target `remote-valgrind' here, and move your stuff
there.
> + * libthread-db-search-path now supports two special values: $sdir and
> $pdir.
This line of change above is not about your patch.
> + + static int
^ a surplus '+'.
> Index: gdb/doc/gdb.texinfo
> ===================================================================
> RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
> retrieving revision 1.838
> diff -c -p -r1.838 gdb.texinfo
> *** gdb/doc/gdb.texinfo 13 May 2011 22:36:07 -0000 1.838
> --- gdb/doc/gdb.texinfo 21 May 2011 19:49:12 -0000
> *************** responses.
> *** 16578,16583 ****
> --- 16578,16595 ----
> Restrict @value{GDBN} to using @var{limit} remote hardware breakpoint or
> watchpoints. A limit of -1, the default, is treated as unlimited.
>
> + @cindex limit hardware watchpoints length
> + @cindex remote target, limit watchpoints length
> + @anchor{set remote hardware-watchpoint-length-limit}
> + @item set remote hardware-watchpoint-length-limit @var{limit}
> + Restrict @value{GDBN} to using @var{limit} bytes for the maximum
> length of
> + a remote hardware watchpoint. A limit of -1, the default, is treated
> + as unlimited.
> + + @item show remote hardware-watchpoint-length-limit
^ a surplus '+'.
--
Yao (é½å°§)
next prev parent reply other threads:[~2011-05-27 3:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-21 22:20 Philippe Waroquiers
2011-05-26 19:02 ` Tom Tromey
2011-05-29 13:01 ` Philippe Waroquiers
2011-05-30 15:26 ` Joel Brobecker
2011-05-31 19:07 ` x86 watchpoints bug (Re: ping: Re: PATCH : allow to set length of hw watchpoints (e.g. for Valgrind gdbserver)) Pedro Alves
2011-05-31 20:25 ` Philippe Waroquiers
2011-05-31 20:53 ` Pedro Alves
2011-05-31 21:29 ` Pedro Alves
2011-05-31 22:15 ` Philippe Waroquiers
2011-05-31 23:04 ` Pedro Alves
2011-06-01 14:35 ` Pedro Alves
2011-06-08 22:55 ` Philippe Waroquiers
2011-06-09 0:00 ` Pedro Alves
2011-06-09 22:16 ` Philippe Waroquiers
2011-07-21 17:20 ` Pedro Alves
2011-07-22 16:40 ` Philippe Waroquiers
2011-07-22 16:43 ` Pedro Alves
2011-07-23 16:28 ` Thiago Jung Bauermann
2011-07-26 20:02 ` software watchpoints bug (was: Re: x86 watchpoints bug) Pedro Alves
2011-07-27 3:45 ` Thiago Jung Bauermann
2011-07-22 17:19 ` x86 watchpoints bug (Re: ping: Re: PATCH : allow to set length of hw watchpoints (e.g. for Valgrind gdbserver)) Pedro Alves
2011-05-27 3:25 ` Yao Qi [this message]
2011-05-27 17:53 ` ping: Re: PATCH : allow to set length of hw watchpoints (e.g. for Valgrind gdbserver) Tom Tromey
2011-05-27 17:59 ` Pedro Alves
2011-05-30 4:06 ` Yao Qi
2011-05-30 5:34 ` Philippe Waroquiers
2011-05-30 5:48 ` Yao Qi
2011-05-30 6:31 ` Philippe Waroquiers
2011-05-31 17:31 ` Pedro Alves
2011-05-31 18:06 ` Philippe Waroquiers
2011-06-01 15:15 ` Pedro Alves
2011-06-05 20:55 ` 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=4DDF196F.5010202@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/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