From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [2/2] RFC: let "commands" affect multiple breakpoints
Date: Thu, 11 Mar 2010 20:50:00 -0000 [thread overview]
Message-ID: <m3pr3ad1ms.fsf@fleche.redhat.com> (raw)
In-Reply-To: <83bpew2i3y.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 10 Mar 2010 19:37:21 +0200")
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>> -@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.
Eli> You never say what is the valid syntax of RANGE. Do I understand
Eli> correctly that RANGE could be "12-34"? Can it also be "1 2 3 4",
Eli> i.e. a list of numbers? What about mixing those ("1-10 25 35")?
Ranges are already described in the parent node, Breakpoints.
Also, none of the other places that use ranges refer to this node.
Tom
next prev parent reply other threads:[~2010-03-11 20:50 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
2010-03-11 20:50 ` Tom Tromey [this message]
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=m3pr3ad1ms.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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