From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb@sources.redhat.com
Subject: Re: FW: [MI] -break-delete with several breakpoints
Date: Fri, 02 May 2008 15:49:00 -0000 [thread overview]
Message-ID: <fvfd5d$hro$1@ger.gmane.org> (raw)
In-Reply-To: <BLU136-W3060478CE85C54ADE5F2BEA0DA0@phx.gbl>
Bjarke Viksoe wrote:
>
>> Vladimir wrote:
>> I've noticed that right now, both -break-delete and -break-disable
>> commands accept several breakpoint ids, like:
>> -break-disable 1 2 3
>> This behaviour comes almost by accident, and is not documented
>> anywhere. The question is -- should we document it and add tests, or
>> should we declare this behaviour does not exist? I would disallow it.
>> Keep it simple ;-)
>
> It's documented alright...
>
> -break-disable ( breakpoint )+
>
> Notice the + character in the MI definition!
Ok, we'll keep it then.
> I'm using this behaviour. Other IDEs would be too, I'd imagine.
For reference, which IDE are you using this behaviour in?
- Volodya
next prev parent reply other threads:[~2008-05-02 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 15:33 Bjarke Viksoe
2008-05-02 15:49 ` Vladimir Prus [this message]
2008-05-03 6:56 Bjarke Viksoe
2008-05-03 14:25 ` Daniel Jacobowitz
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='fvfd5d$hro$1@ger.gmane.org' \
--to=vladimir@codesourcery.com \
--cc=gdb@sources.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