This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [MI non-stop 07/11, RFA] Allow all CLI command even if target is executing.
- From: Pedro Alves <pedro at codesourcery dot com>
- To: Daniel Jacobowitz <drow at false dot org>
- Cc: Vladimir Prus <vladimir at codesourcery dot com>, gdb-patches at sourceware dot org
- Date: Fri, 11 Jul 2008 20:12:33 +0100
- Subject: Re: [MI non-stop 07/11, RFA] Allow all CLI command even if target is executing.
- References: <200806282055.45829.vladimir@codesourcery.com> <200807112258.25104.vladimir@codesourcery.com> <20080711190421.GA23117@caradoc.them.org>
A Friday 11 July 2008 20:04:21, Daniel Jacobowitz wrote:
> On Fri, Jul 11, 2008 at 10:58:24PM +0400, Vladimir Prus wrote:
> > I've of the same opinion. It seems to me that examining each and every
> > command is not quite practical. So, we either get to enable all commands
> > and then disable, or clarify error messages, or disable all commands, and
> > enable those that actually have to work. Enabling all commands seems
> > safer, since the worst problem is inaccurate error message.
> Well, or inconsistent data structures or assertion failures if
> something changes underneath... anyway, good enough for me; it's OK.
> Does this make the command flag obsolete?
That has an easy workaround. Don't call the command. Disabling a
command that would otherwise execute fine does not have a workaround
(at least currently it doesn't).
--
Pedro Alves