public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Phil Muldoon <pmuldoon@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tromey@redhat.com, pedro@codesourcery.com,
	gdb-patches@sourceware.org,        dan@codesourcery.com
Subject: Re: [patch] Add visible flag to breakpoints.
Date: Fri, 22 Oct 2010 21:37:00 -0000	[thread overview]
Message-ID: <m3wrp96h9s.fsf@redhat.com> (raw)
In-Reply-To: <83aam59aot.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 22 Oct	2010 23:31:14 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Phil Muldoon <pmuldoon@redhat.com>
>> Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org,        dan@codesourcery.com
>> Date: Fri, 22 Oct 2010 22:05:30 +0100
>> 
>> I decided to add internal watchpoint support.  I've also added the other
>> changes requested.
>> 
>> OK?
>
> Thanks.
>
>> -/* Set a breakpoint.  This function is shared between CLI and MI
>> +/* Set a breakpoint. This function is shared between CLI and MI
>
> Why did you need to remove one of the two spaces between these
> sentences?

I didn't, this was an error. Thanks for catching.

>
>>     functions for setting a breakpoint.  This function has two major
>>     modes of operations, selected by the PARSE_CONDITION_AND_THREAD
>>     parameter.  If non-zero, the function will parse arg, extracting
>>     breakpoint location, address and thread. Otherwise, ARG is just the
>>     location of breakpoint, with condition and thread specified by the
>> -   COND_STRING and THREAD parameters.  Returns true if any breakpoint
>> -   was created; false otherwise.  */
>> -
>> +   COND_STRING and THREAD parameters.  If INTERNAL is non-zero, the
>> +   breakpoint number will be allocated from the internal breakpoint
>> +   count.   Returns true if any breakpoint was created; false
>             ^^^
> And here you have 3 instead of 2.

Thanks

>> +@code{maint info breakpoints} command).  The optional @var{wp_class}
>>  argument defines the class of watchpoint to create, if @var{type} is
>>  defined as @code{BP_WATCHPOINT}.
>
> "if @var{type} is @code{BP_WATCHPOINT}" is simpler and more clear, IMO.

Thanks.

>> +@defivar Breakpoint visible
>> +This attribute holds the breakpoint's visibility flag---the identifier used to
>> +determine whether the breakpoint is visible to the user when set, or
>> +when the @samp{info breakpoints} command is run.
>
> There's no need to go through identifiers.  How about this rewording?
>
>   This attribute tells whether the breakpoint is visible to the user
>   when set, or when the @samp{info breakpoints} command is run.
>

Works for me.

Cheers,

Phil

  reply	other threads:[~2010-10-22 21:37 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
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 [this message]
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=m3wrp96h9s.fsf@redhat.com \
    --to=pmuldoon@redhat.com \
    --cc=dan@codesourcery.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).