From fecf1c0074572e34965a1b83dc9440b9b892d7a0 Mon Sep 17 00:00:00 2001 From: Aditya Gupta Date: Wed, 28 Jun 2023 11:38:48 +0530 Subject: [PATCH] remove 'frame' from prohibited commands list MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Currently, 'frame' is prohibited on every architecture, even in gdb mode. Since the passthrough is working on few architectures (eg. ppc64, and vmss x86_64), so remove it from prohibited list, so that 'frame' command can be used This has an implication on all architectures, that 'frame' now outputs this in default mode: ``` crash> frame #0 in ?? () ``` instead of the before prohibited message ``` crash> frame crash: prohibited gdb command: frame ``` Though, 'frame' should work in gdb mode for architectures that implement 'machdep->get_cpu_reg' Cc: Sourabh Jain Cc: Hari Bathini Cc: Mahesh J Salgaonkar Cc: Naveen N. Rao Cc: Lianbo Jiang Cc: HAGIO KAZUHITO(萩尾 一仁) Cc: Tao Liu Signed-off-by: Aditya Gupta --- gdb_interface.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gdb_interface.c b/gdb_interface.c index b14319c6..8f99a0d7 100644 --- a/gdb_interface.c +++ b/gdb_interface.c @@ -711,7 +711,7 @@ static char *prohibited_list[] = { "watch", "rwatch", "awatch", "attach", "continue", "c", "fg", "detach", "finish", "handle", "interrupt", "jump", "kill", "next", "nexti", "signal", "step", "s", "stepi", "target", "until", "delete", - "clear", "disable", "enable", "condition", "ignore", "frame", "catch", + "clear", "disable", "enable", "condition", "ignore", "catch", "tcatch", "return", "file", "exec-file", "core-file", "symbol-file", "load", "si", "ni", "shell", "sy", NULL /* must be last */