From: "Philippe Waroquiers" <philippe.waroquiers@skynet.be>
To: "Tom Tromey" <tromey@redhat.com>
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: Fri, 11 Mar 2011 07:58:00 -0000 [thread overview]
Message-ID: <1EA6FE6B4A03417898402C2C707CADAB@soleil> (raw)
In-Reply-To: <m3bp1iadtt.fsf@fleche.redhat.com>
> 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.
This is for sure the best approach. This would be a new approach,
that would be a general solution, matching various hardware (and
not only the "Valgrind hardware"). I suppose the same approach
should be done for "non remote" hardware watchpoints.
What I have added to gdb follows the current logic, i.e. mostly
"assume the best, and if it fails, tell the user so that limits can be
reduced and/or can decide to switch to software breakpoints".
I will prepare a patch with what I have done.
Philippe
next prev parent reply other threads:[~2011-03-11 7:58 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
2011-03-11 7:58 ` Philippe Waroquiers [this message]
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=1EA6FE6B4A03417898402C2C707CADAB@soleil \
--to=philippe.waroquiers@skynet.be \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=jseward@acm.org \
--cc=robertsong.japan@gmail.com \
--cc=tromey@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