Use gdbpy_convert_exception in a few more spots
I noticed a few places were converting a gdb exception to a Python exception "by hand". It's better to use the existing gdbpy_convert_exception helper function, as this handles memory errors correctly, and in the future may be enhanced in other ways. gdb/ChangeLog 2018-12-27 Tom Tromey <tom@tromey.com> * python/py-value.c (convert_value_from_python): Use gdbpy_convert_exception. * python/py-param.c (parmpy_init): Use gdbpy_convert_exception. * python/py-cmd.c (cmdpy_init): Use gdbpy_convert_exception. * python/py-breakpoint.c (bppy_init): Use gdbpy_convert_exception.
This commit is contained in:
parent
6987262214
commit
ec9c2750b7
5 changed files with 13 additions and 12 deletions
|
@ -874,9 +874,7 @@ bppy_init (PyObject *self, PyObject *args, PyObject *kwargs)
|
|||
CATCH (except, RETURN_MASK_ALL)
|
||||
{
|
||||
bppy_pending_object = NULL;
|
||||
PyErr_Format (except.reason == RETURN_QUIT
|
||||
? PyExc_KeyboardInterrupt : PyExc_RuntimeError,
|
||||
"%s", except.message);
|
||||
gdbpy_convert_exception (except);
|
||||
return -1;
|
||||
}
|
||||
END_CATCH
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue