Allow setting a parameter to raise gdb.GdbError
A convention in the Python layer is that raising a gdb.GdbError will not print the Python stack -- instead the exception is treated as any other gdb exception. PR python/18852 asks that this treatment be extended the the get_set_value method of gdb.Parameter. This makes sense, because it lets Python-created parameters act like gdb parameters. 2018-09-23 Tom Tromey <tom@tromey.com> PR python/18852: * python/py-param.c (get_set_value): Use gdbpy_handle_exception. gdb/doc/ChangeLog 2018-09-23 Tom Tromey <tom@tromey.com> PR python/18852: * python.texi (Parameters In Python): Document exception behavior of get_set_string. gdb/testsuite/ChangeLog 2018-09-23 Tom Tromey <tom@tromey.com> PR python/18852: * gdb.python/py-parameter.exp: Add test for parameter that throws on "set".
This commit is contained in:
parent
2b4ad2fe43
commit
ae778caf09
6 changed files with 57 additions and 4 deletions
|
@ -396,10 +396,7 @@ get_set_value (const char *args, int from_tty,
|
|||
{
|
||||
set_doc_string = call_doc_function (obj, set_doc_func.get (), NULL);
|
||||
if (! set_doc_string)
|
||||
{
|
||||
gdbpy_print_stack ();
|
||||
return;
|
||||
}
|
||||
gdbpy_handle_exception ();
|
||||
}
|
||||
|
||||
const char *str = set_doc_string.get ();
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue