aboutsummaryrefslogtreecommitdiff
path: root/gdb/tui
diff options
context:
space:
mode:
authorPedro Alves <pedro@palves.net>2023-01-27 18:07:56 +0000
committerPedro Alves <pedro@palves.net>2023-02-08 17:28:42 +0000
commitb885aea1bb987435929b4298982ac6fc27f69403 (patch)
treeb2db58e6f0bf93350ea3eb52d1bb6bfc8ca41c44 /gdb/tui
parentcdeb7b7de286078a1a0733a5cc9672c566917d61 (diff)
downloadgdb-b885aea1bb987435929b4298982ac6fc27f69403.zip
gdb-b885aea1bb987435929b4298982ac6fc27f69403.tar.gz
gdb-b885aea1bb987435929b4298982ac6fc27f69403.tar.bz2
Simplify interp::exec / interp_exec - let exceptions propagate
This patch implements a simplication that I suggested here: https://sourceware.org/pipermail/gdb-patches/2022-March/186320.html Currently, the interp::exec virtual method interface is such that subclass implementations must catch exceptions and then return them via normal function return. However, higher up the in chain, for the CLI we get to interpreter_exec_cmd, which does: for (i = 1; i < nrules; i++) { struct gdb_exception e = interp_exec (interp_to_use, prules[i]); if (e.reason < 0) { interp_set (old_interp, 0); error (_("error in command: \"%s\"."), prules[i]); } } and for MI we get to mi_cmd_interpreter_exec, which has: void mi_cmd_interpreter_exec (const char *command, char **argv, int argc) { ... for (i = 1; i < argc; i++) { struct gdb_exception e = interp_exec (interp_to_use, argv[i]); if (e.reason < 0) error ("%s", e.what ()); } } Note that if those errors are reached, we lose the original exception's error code. I can't see why we'd want that. And, I can't see why we need to have interp_exec catch the exception and return it via the normal return path. That's normally needed when we need to handle propagating exceptions across C code, like across readline or ncurses, but that's not the case here. It seems to me that we can simplify things by removing some try/catch-ing and just letting exceptions propagate normally. Note, the "error in command" error shown above, which only exists in the CLI interpreter-exec command, is only ever printed AFAICS if you run "interpreter-exec console" when the top level interpreter is already the console/tui. Like: (gdb) interpreter-exec console "foobar" Undefined command: "foobar". Try "help". error in command: "foobar". You won't see it with MI's "-interpreter-exec console" from a top level MI interpreter: (gdb) -interpreter-exec console "foobar" &"Undefined command: \"foobar\". Try \"help\".\n" ^error,msg="Undefined command: \"foobar\". Try \"help\"." (gdb) nor with MI's "-interpreter-exec mi" from a top level MI interpreter: (gdb) -interpreter-exec mi "-foobar" ^error,msg="Undefined MI command: foobar",code="undefined-command" ^done (gdb) in both these cases because MI's -interpreter-exec just does: error ("%s", e.what ()); You won't see it either when running an MI command with the CLI's "interpreter-exec mi": (gdb) interpreter-exec mi "-foobar" ^error,msg="Undefined MI command: foobar",code="undefined-command" (gdb) This last case is because MI's interp::exec implementation never returns an error: gdb_exception mi_interp::exec (const char *command) { mi_execute_command_wrapper (command); return gdb_exception (); } Thus I think that "error in command" error is pretty pointless, and since it simplifies things to not have it, the patch just removes it. The patch also ends up addressing an old FIXME. Change-Id: I5a6432a80496934ac7127594c53bf5221622e393 Approved-By: Tom Tromey <tromey@adacore.com> Approved-By: Kevin Buettner <kevinb@redhat.com>
Diffstat (limited to 'gdb/tui')
-rw-r--r--gdb/tui/tui-interp.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/gdb/tui/tui-interp.c b/gdb/tui/tui-interp.c
index 3c28145..812c62c 100644
--- a/gdb/tui/tui-interp.c
+++ b/gdb/tui/tui-interp.c
@@ -49,7 +49,7 @@ public:
void init (bool top_level) override;
void resume () override;
void suspend () override;
- gdb_exception exec (const char *command_str) override;
+ void exec (const char *command_str) override;
ui_out *interp_ui_out () override;
};
@@ -149,7 +149,7 @@ tui_interp::interp_ui_out ()
return tui_old_uiout;
}
-gdb_exception
+void
tui_interp::exec (const char *command_str)
{
internal_error (_("tui_exec called"));