mirror of
https://sourceware.org/git/binutils-gdb.git
synced 2025-01-06 12:09:26 +08:00
Allow Python commands to be in class_tui
Now that Python code can create TUI windows, it seemed appropriate to allow Python commands to appear in the "TUI" help class. This patch adds this capability. gdb/ChangeLog 2020-04-28 Tom Tromey <tom@tromey.com> * NEWS: Update. * python/py-cmd.c (gdbpy_initialize_commands): Add COMMAND_TUI. (cmdpy_init): Allow class_tui. gdb/doc/ChangeLog 2020-04-28 Tom Tromey <tom@tromey.com> * python.texi (Commands In Python): Document gdb.COMMAND_TUI.
This commit is contained in:
parent
a65189c980
commit
2b2fbab8ef
@ -1,3 +1,9 @@
|
||||
2020-04-28 Tom Tromey <tom@tromey.com>
|
||||
|
||||
* NEWS: Update.
|
||||
* python/py-cmd.c (gdbpy_initialize_commands): Add COMMAND_TUI.
|
||||
(cmdpy_init): Allow class_tui.
|
||||
|
||||
2020-04-28 Mark Williams <mark@myosotissp.com>
|
||||
|
||||
PR gdb/24480
|
||||
|
3
gdb/NEWS
3
gdb/NEWS
@ -73,6 +73,9 @@ GNU/Linux/RISC-V (gdbserver) riscv*-*-linux*
|
||||
field of a dynamic type may have None for its "bitpos" attribute
|
||||
as well.
|
||||
|
||||
** Commands written in Python can be in the "TUI" help class by
|
||||
registering with the new constant gdb.COMMAND_TUI.
|
||||
|
||||
*** Changes in GDB 9
|
||||
|
||||
* 'thread-exited' event is now available in the annotations interface.
|
||||
|
@ -1,3 +1,7 @@
|
||||
2020-04-28 Tom Tromey <tom@tromey.com>
|
||||
|
||||
* python.texi (Commands In Python): Document gdb.COMMAND_TUI.
|
||||
|
||||
2020-04-27 Tom Tromey <tromey@adacore.com>
|
||||
|
||||
* python.texi (Types In Python): Mention missing fields. Add
|
||||
|
@ -3829,6 +3829,13 @@ The command has to do with tracepoints. For example, @code{trace},
|
||||
@kbd{help tracepoints} at the @value{GDBN} prompt to see a list of
|
||||
commands in this category.
|
||||
|
||||
@findex COMMAND_TUI
|
||||
@findex gdb.COMMAND_TUI
|
||||
@item gdb.COMMAND_TUI
|
||||
The command has to do with the text user interface (@pxref{TUI}).
|
||||
Type @kbd{help tui} at the @value{GDBN} prompt to see a list of
|
||||
commands in this category.
|
||||
|
||||
@findex COMMAND_USER
|
||||
@findex gdb.COMMAND_USER
|
||||
@item gdb.COMMAND_USER
|
||||
|
@ -465,7 +465,8 @@ cmdpy_init (PyObject *self, PyObject *args, PyObject *kw)
|
||||
&& cmdtype != class_files && cmdtype != class_support
|
||||
&& cmdtype != class_info && cmdtype != class_breakpoint
|
||||
&& cmdtype != class_trace && cmdtype != class_obscure
|
||||
&& cmdtype != class_maintenance && cmdtype != class_user)
|
||||
&& cmdtype != class_maintenance && cmdtype != class_user
|
||||
&& cmdtype != class_tui)
|
||||
{
|
||||
PyErr_Format (PyExc_RuntimeError, _("Invalid command class argument."));
|
||||
return -1;
|
||||
@ -593,8 +594,7 @@ gdbpy_initialize_commands (void)
|
||||
if (PyType_Ready (&cmdpy_object_type) < 0)
|
||||
return -1;
|
||||
|
||||
/* Note: alias and user are special; pseudo appears to be unused,
|
||||
and there is no reason to expose tui, I think. */
|
||||
/* Note: alias and user are special. */
|
||||
if (PyModule_AddIntConstant (gdb_module, "COMMAND_NONE", no_class) < 0
|
||||
|| PyModule_AddIntConstant (gdb_module, "COMMAND_RUNNING", class_run) < 0
|
||||
|| PyModule_AddIntConstant (gdb_module, "COMMAND_DATA", class_vars) < 0
|
||||
@ -611,7 +611,8 @@ gdbpy_initialize_commands (void)
|
||||
class_obscure) < 0
|
||||
|| PyModule_AddIntConstant (gdb_module, "COMMAND_MAINTENANCE",
|
||||
class_maintenance) < 0
|
||||
|| PyModule_AddIntConstant (gdb_module, "COMMAND_USER", class_user) < 0)
|
||||
|| PyModule_AddIntConstant (gdb_module, "COMMAND_USER", class_user) < 0
|
||||
|| PyModule_AddIntConstant (gdb_module, "COMMAND_TUI", class_tui) < 0)
|
||||
return -1;
|
||||
|
||||
for (i = 0; i < N_COMPLETERS; ++i)
|
||||
|
Loading…
Reference in New Issue
Block a user