This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Fix 'Undefined command' error message
On Wed, Nov 23, 2005 at 09:53:46PM +0200, Eli Zaretskii wrote:
> > Date: Wed, 23 Nov 2005 14:19:40 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: Eli Zaretskii <eliz@gnu.org>, schwab@suse.de,
> > gdb-patches@sources.redhat.com
> >
> > > The TUI does *not* avoid the problems pointed out by Andreas. 'u+1' must
> > > be written 'u +1'. The latter syntax seems more correct to me in any
> > > case - the '+' is part of the operand, not the command. That said, many
> > > people are probably used to using the command like Andreas.
> >
> > I had no idea this was possible (or what it did, until I tried it)... I
> > wouldn't cry about breaking it if there was any benefit.
>
> Sorry, Daniel, I don't think I get what you mean. Could you please
> elaborate on what you suggest we do?
"u+1" in current versions of GDB is the same as "until +1" or "u +1",
which is "until the next source line". I don't believe this is
documented behavior, and I also don't think it's particularly valuable
behavior - just an implementation accident. So if "u+1" returned
'unknown command "u+1"' instead, I think that would be an acceptable
change, especially if it reduces some special-cases in the handling
of commands.
Right now it works in CLI, but not in TUI:
(gdb) u+1
Undefined command: "u". Try "help".
--
Daniel Jacobowitz
CodeSourcery, LLC