diff options
| author | Tom Tromey <tom@tromey.com> | 2018-12-25 11:00:21 -0700 |
|---|---|---|
| committer | Tom Tromey <tom@tromey.com> | 2018-12-27 13:34:38 -0700 |
| commit | ec9c2750b7bab8a55aaf7d2386e809d4e81deb03 (patch) | |
| tree | 043b8260bb43cb0d5db54a1c089c8d3d6c0c554b /gdb/selftest.m4 | |
| parent | 6987262214a204ea3ab857d86a1faf9f4e66f211 (diff) | |
| download | gdb-ec9c2750b7bab8a55aaf7d2386e809d4e81deb03.zip gdb-ec9c2750b7bab8a55aaf7d2386e809d4e81deb03.tar.gz gdb-ec9c2750b7bab8a55aaf7d2386e809d4e81deb03.tar.bz2 | |
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.
Diffstat (limited to 'gdb/selftest.m4')
0 files changed, 0 insertions, 0 deletions