Use gdbpy_convert_exception in a few more spots
authorTom Tromey <tom@tromey.com>
Tue, 25 Dec 2018 18:00:21 +0000 (11:00 -0700)
committerTom Tromey <tom@tromey.com>
Thu, 27 Dec 2018 20:34:38 +0000 (13:34 -0700)
commitec9c2750b7bab8a55aaf7d2386e809d4e81deb03
tree043b8260bb43cb0d5db54a1c089c8d3d6c0c554b
parent6987262214a204ea3ab857d86a1faf9f4e66f211
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.
gdb/ChangeLog
gdb/python/py-breakpoint.c
gdb/python/py-cmd.c
gdb/python/py-param.c
gdb/python/py-value.c