From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Re: [PATCH] Forbid watchpoint on a constant value
Date: Fri, 21 May 2010 00:09:00 -0000 [thread overview]
Message-ID: <201005202054.53548.sergiodj@redhat.com> (raw)
In-Reply-To: <20100520233449.GO3019@adacore.com>
On Thursday 20 May 2010 20:34:49, Joel Brobecker wrote:
> > Thanks for your review. I don't really have a strong opinion about it,
> > but your suggestion sounds pretty reasonable to me. Since Jan is the
> > co-author of this patch, I'll wait to see what he thinks about it.
>
> I don't have a strong opinion on it either, which is why I am interested
> in other people's thoughts on it. What was your own motivation behind
> this? I guess some user inserted a watchpoint on something constant,
> and then waited for ages for the watchpoint to trigger, thinking that
> the slowness was due to the watchpoint, not his, er... silliness :-P?
The patch was in our internal tree for a while (Jan has written the first
version of it), so I don't really know his motivations behind it. But the
scenario you described may not be that rare :-).
FWIW, I actually was thinking a little more about the subject, and I agree
with your suggestion. GDB may not forbid the user to do what he wants (even
if that appears to be totally non-sense). I think a warning message, in this
case, is the best option indeed. If Jan agrees with that, I'll submit a
refreshed version of the patch with that modification (along with the other
ones that I promised).
Thanks,
--
Sergio Durigan Junior
Red Hat
next prev parent reply other threads:[~2010-05-20 23:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 17:36 Sergio Durigan Junior
2010-05-18 17:49 ` Eli Zaretskii
2010-05-18 19:24 ` Sergio Durigan Junior
2010-05-18 23:08 ` Jan Kratochvil
2010-05-18 23:50 ` Sergio Durigan Junior
2010-05-19 20:26 ` Jan Kratochvil
2010-05-20 6:21 ` Sergio Durigan Junior
2010-05-20 15:50 ` Jan Kratochvil
2010-05-20 16:24 ` Sergio Durigan Junior
2010-05-20 17:03 ` Jan Kratochvil
2010-05-20 17:06 ` Sergio Durigan Junior
2010-05-27 21:54 ` Tom Tromey
2010-05-20 23:23 ` Joel Brobecker
2010-05-20 23:31 ` Sergio Durigan Junior
2010-05-20 23:55 ` Joel Brobecker
2010-05-21 0:09 ` Sergio Durigan Junior [this message]
2010-05-21 7:05 ` Eli Zaretskii
2010-05-21 8:44 ` Jan Kratochvil
2010-05-21 21:43 ` Sergio Durigan Junior
2010-05-21 22:20 ` Sergio Durigan Junior
2010-05-29 0:04 ` Joel Brobecker
2010-06-04 13:54 ` Jan Kratochvil
2010-06-04 16:49 ` Tom Tromey
2010-06-05 5:35 ` Sergio Durigan Junior
2010-06-05 14:38 ` Jan Kratochvil
2010-06-06 0:20 ` Sergio Durigan Junior
2010-06-15 17:30 ` Tom Tromey
2010-06-16 18:33 ` Sergio Durigan Junior
2010-06-16 18:36 ` Jan Kratochvil
2010-05-28 5:12 ` Tom Tromey
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=201005202054.53548.sergiodj@redhat.com \
--to=sergiodj@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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