Re: PR8554: New command to save breakpoints to a file

[Pedro Alves <pedro at codesourcery dot com>]

On Thursday 15 April 2010 23:49:32, Michael Snyder wrote:
> BTW. "save_command" needs to print an error or something, not
> simply return without doing anything.  If I type "save<return>",
> I get a silent failure.

I think the common practice is to have it print "help save".
At least, there are over 30 calls to help_list under gdb/
that look like that.  E.g.,

(gdb) set print
"set print" must be followed by the name of a print subcommand.
List of set print subcommands:

set print address -- Set printing of addresses
...

I'll do that.


I don't think we should bother with aliasing save to 
save-tracepoints, and it may even be annoying at some
point.

-- 
Pedro Alves