History

kgdb: gdb "monitor" -> kdb passthrough

One of the driving forces behind integrating another front end (kdb) to the debug core is to allow front end commands to be accessible via gdb's monitor command. It is true that you could write gdb macros to get certain data, but you may want to just use gdb to access the commands that are available in the kdb front end. This patch implements the Rcmd gdb stub packet. In gdb you access this with the "monitor" command. For instance you could type "monitor help", "monitor lsmod" or "monitor ps A" etc... There is no error checking or command restrictions on what you can and cannot access at this point. Doing something like trying to set breakpoints with the monitor command is going to cause nothing but problems. Perhaps in the future only the commands that are actually known to work with the gdb monitor command will be available.

Jason Wessel committed 16 years ago

Commit a0de0551 parent 6d45a1a5 files · +34 −6Browse files

Showing the changes to kernel/debug/debug_core.c (1 of 5 files). Show all

Unified · Split

kernel/debug/debug_core.c+1−1
@@ -82,7 +82,7 @@ static int kgdb_use_con; · 81 unmodified lines
8282 int dbg_switch_cpu;
8383
8484 /* Use kdb or gdbserver mode */
85−static int dbg_kdb_mode = 1;
85+int dbg_kdb_mode = 1;
8686
8787 static int __init opt_kgdb_con(char *str)
8888 {