public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org, pmuldoon@redhat.com
Cc: dan@codesourcery.com
Subject: Re: [patch] Add visible flag to breakpoints.
Date: Sat, 16 Oct 2010 19:03:00 -0000	[thread overview]
Message-ID: <201010162003.41609.pedro@codesourcery.com> (raw)
In-Reply-To: <m3zkuo3hmy.fsf@redhat.com>

Below's just for the record.  I'm okay with whatever you guys
have decided.  ;-)

On Friday 08 October 2010 15:04:37, Phil Muldoon wrote:
> Pedro Alves <pedro@codesourcery.com> writes:
> 
> > On Friday 08 October 2010 13:50:34, Phil Muldoon wrote:
> >> The @var{internal} argument has no effect with watchpoints.
> >
> > Should it be an error instead (or made to work)?
> 
> I can make it an error.  I decided not to do watchpoints.  

IMO, either of these would be better API than a silent ignore.
If you go with error, the client of the API can
retry a non-internal breakpoint after e.g., printing a warning,
say.  As is, if you ever add support for internal watchpoints,
then a script has no way to tell whether such internal breakpoints
are actually supported by the gdb at hand until trying: if the flag
is just ignored, too late, the user has already seen the
breakpoint being created...

> The
> consequences of setting hidden watchpoints from a script that could turn
> out to be software watchpoints seemed a little troubling. 

IMO, it should the script writers' responsibility to weight that,
but it's also okay to not support it until someone asks for it
(though that someone would be happier if she didn't have to,
obviously :-) ).

-- 
Pedro Alves

  parent reply	other threads:[~2010-10-16 19:03 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-30 16:28 Phil Muldoon
2010-09-30 16:41 ` Daniel Jacobowitz
2010-09-30 17:51   ` Phil Muldoon
2010-09-30 17:55     ` Pedro Alves
2010-09-30 18:12       ` Phil Muldoon
2010-10-08 12:51       ` Phil Muldoon
2010-10-08 13:35         ` Pedro Alves
2010-10-08 14:04           ` Phil Muldoon
2010-10-08 18:44             ` Tom Tromey
2010-10-12 20:25               ` Phil Muldoon
2010-10-12 21:34                 ` Tom Tromey
2010-10-13 12:45                   ` Phil Muldoon
2010-10-13 13:06                     ` Phil Muldoon
2010-10-13 15:36                     ` Tom Tromey
2010-10-16 18:42                     ` Pedro Alves
2010-10-16 19:03             ` Pedro Alves [this message]
2010-10-18 16:09               ` Tom Tromey
2010-10-22 21:05                 ` Phil Muldoon
2010-10-22 21:31                   ` Eli Zaretskii
2010-10-22 21:37                     ` Phil Muldoon
2010-10-23  9:07                       ` Eli Zaretskii
2010-10-31 21:07                   ` Pedro Alves
2010-11-11 14:36                     ` Phil Muldoon
2010-11-12 12:43                       ` Ken Werner
2010-11-12 12:49                         ` Pedro Alves
2010-11-12 12:58                           ` Ken Werner
2010-10-08 18:40         ` Tom Tromey
2010-09-30 17:04 ` Pedro Alves
2010-09-30 17:55   ` Phil Muldoon
2010-09-30 17:51 ` Eli Zaretskii
2010-10-05 22:28 ` 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=201010162003.41609.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=dan@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pmuldoon@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).