Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: tromey@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: [2/2] RFC: let "commands" affect multiple breakpoints
Date: Wed, 10 Mar 2010 17:37:00 -0000	[thread overview]
Message-ID: <83bpew2i3y.fsf@gnu.org> (raw)
In-Reply-To: <m31vfsltl7.fsf@fleche.redhat.com>

> From: Tom Tromey <tromey@redhat.com>
> Date: Tue, 09 Mar 2010 20:54:28 -0700
> 
>  *** Changes since GDB 7.1
>  
> +* The `commands' command now accepts a range of breakpoints to modify.
> +  A plain `commands' following an `rbreak' will affect all the
> +  breakpoints set by `rbreak'.

This is okay, but maybe it will need a slight modification, see
below.

> -@item commands @r{[}@var{bnum}@r{]}
> +@item commands @r{[}@var{range}@dots{}@r{]}
>  @itemx @dots{} @var{command-list} @dots{}
>  @itemx end
> -Specify a list of commands for breakpoint number @var{bnum}.  The commands
> +Specify a list of commands for the given breakpoints.  The commands
>  themselves appear on the following lines.  Type a line containing just
>  @code{end} to terminate the commands.

You never say what is the valid syntax of RANGE.  Do I understand
correctly that RANGE could be "12-34"?  Can it also be "1 2 3 4",
i.e. a list of numbers?  What about mixing those ("1-10 25 35")?

Depending on the answers, the NEWS entry might need some clarification
or maybe just an example.

Thanks.


  parent reply	other threads:[~2010-03-10 17:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10  3:54 Tom Tromey
2010-03-10 16:34 ` Tom Tromey
2010-03-10 17:05 ` Pedro Alves
2010-03-11 21:42   ` Tom Tromey
2010-03-23  4:23     ` Tom Tromey
2010-03-23 17:24       ` Eli Zaretskii
2010-03-24 21:21       ` Tom Tromey
2010-03-25 17:09         ` Pedro Alves
2010-03-30 20:42           ` Tom Tromey
2010-04-01 11:47             ` Pedro Alves
2010-04-01 13:32               ` Eli Zaretskii
2010-03-10 17:37 ` Eli Zaretskii [this message]
2010-03-11 20:50   ` Tom Tromey
2010-03-12  7:53     ` Eli Zaretskii

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=83bpew2i3y.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --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