This is the mail archive of the
mailing list for the GDB project.
Re: [MI] -break-delete with several breakpoints
- From: AndrÃ PÃnitz <apoenitz at trolltech dot com>
- To: gdb at sourceware dot org
- Date: Mon, 28 Apr 2008 10:03:38 +0200
- Subject: Re: [MI] -break-delete with several breakpoints
- References: <firstname.lastname@example.org>
On Saturday 26 April 2008 20:08:50 Vladimir Prus 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 ;-)
> I think that most of the time, making use of this behaviour will require
> explicit code in the frontend, and the question is if that makes sense.
I doubt it would. I could as well fire off three separate commands.
As that would not require extra roundtrips, that's basically 'free'.
> Say, for -var-update accepting a list of variable object might be good idea,
> since the number of variable object can be significant, and they are updated
> on each step. For deleting and disabling breakpoints, I'm actually not sure.
> Typically, there are few breakpoints and wholesale delete is not common,
> so it's not worth optimizing for.
I fully agree.