From 95f86e8e0525fc93093cc2bc060df5017d2f504e Mon Sep 17 00:00:00 2001 From: =?utf8?q?=C3=98yvind=20Harboe?= Date: Tue, 5 Jan 2010 14:57:45 +0100 Subject: [PATCH] gdb: fix regression in gdb_port command MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit 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. Regression was introduced in: b3bf1d12b2fdfba1c1cbee3e1afbfbb27cbd1a26 aka v0.4.0-rc1-32-gb3bf1d1 Signed-off-by: Øyvind Harboe --- src/server/gdb_server.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/server/gdb_server.c b/src/server/gdb_server.c index d5d7042c..96b9dbf1 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 = "", }, { -- 2.39.5