From: Tom Tromey <tromey@redhat.com>
To: "Philippe Waroquiers" <philippe.waroquiers@skynet.be>
Cc: "Jan Kratochvil" <jan.kratochvil@redhat.com>,
"robert song" <robertsong.japan@gmail.com>,
<gdb@sourceware.org>, "Julian Seward" <jseward@acm.org>
Subject: Re: Why no hwatch command in gdb ?
Date: Thu, 10 Mar 2011 21:04:00 -0000 [thread overview]
Message-ID: <m3bp1iadtt.fsf@fleche.redhat.com> (raw)
In-Reply-To: <FD8E0CA1171A4A4AAD80B5E5C0747567@soleil> (Philippe Waroquiers's message of "Thu, 10 Mar 2011 15:47:07 +0100")
>>>>> "Philippe" == Philippe Waroquiers <philippe.waroquiers@skynet.be> writes:
Philippe> On the side of 'hardware' watchpoints limitations:
Philippe> I am busy embedding a gdbserver inside Valgrind (target is
Philippe> to integrate it in April, but more review activity is still needed).
Delightful.
Philippe> I only encountered a small problem with gdb "remote": There is
Philippe> a gdb command to configure the nr of remote hardware
Philippe> watchpoint but there is no command to configure the length for
Philippe> an hardware watchpoint: e.g. for i386, gdb remote "hardcodes"
Philippe> the length to 4 bytes (which looks wrong btw, as the real hw
Philippe> can go up to 8 bytes I believe).
Philippe> So, I have in a corner a patch implementing
Philippe> 'set remote hardware-watchpoint-length-limit'
Philippe> to configure the max length limit of an hw watchpoint.
Philippe> I believe it would be nice to add this new command in gdb.
As far as I understand it, this sounds ok.
Why can't this be negotiated between gdb and the remote?
Then the in-valgrind gdbserver could just report unlimited and the user
wouldn't have to fool around.
Philippe> If you want more info about the gdbserver in Valgrind, I can
Philippe> give more (I expect to output a new improved beta version of
Philippe> the Valgrind gdbserver patch in the coming days).
If you send out announcements, feel free to CC this list.
Tom
next prev parent reply other threads:[~2011-03-10 21:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 7:25 robert song
2011-03-10 8:12 ` Jan Kratochvil
2011-03-10 10:09 ` robert song
2011-03-10 10:34 ` Jan Kratochvil
2011-03-10 11:26 ` Eli Zaretskii
2011-03-10 11:34 ` Joel Brobecker
2011-03-10 12:27 ` Pedro Alves
2011-03-10 11:55 ` Jan Kratochvil
2011-03-10 14:47 ` Frank Ch. Eigler
2011-03-10 12:18 ` robert song
2011-03-10 13:45 ` Jan Kratochvil
2011-03-10 14:47 ` Philippe Waroquiers
2011-03-10 21:04 ` Tom Tromey [this message]
2011-03-11 7:58 ` Philippe Waroquiers
2011-03-11 17:48 ` Daniel Jacobowitz
2011-03-10 8:23 paawan oza
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=m3bp1iadtt.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=jseward@acm.org \
--cc=philippe.waroquiers@skynet.be \
--cc=robertsong.japan@gmail.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