From: Øyvind Harboe <[email protected]> The gdb_port command can be invoked during normal execution to report the port used for gdb, whereas it was listed as CONFIG stage only, which caused an error when excuting it to return the reported error.
Also in line with the grander goal of making more commands available during all "modes" (perhaps retiring config mode), there is no particular reason to limit gdb_port to the config stage. Signed-off-by: Øyvind Harboe <[email protected]> --- src/server/gdb_server.c | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/src/server/gdb_server.c b/src/server/gdb_server.c index d5d7042..96b9dbf 100644 --- a/src/server/gdb_server.c +++ b/src/server/gdb_server.c @@ -2421,8 +2421,9 @@ static const struct command_registration gdb_command_handlers[] = { { .name = "gdb_port", .handler = &handle_gdb_port_command, - .mode = COMMAND_CONFIG, - .help = "daemon configuration command gdb_port", + .mode = COMMAND_ANY, + .help = "daemon configuration command gdb_port. No arguments reports " + "GDB port.", .usage = "<port>", }, { -- 1.6.3.3 _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
