Simplify gdbpy_stop_recording
authorTom Tromey <tom@tromey.com>
Thu, 27 Dec 2018 18:57:28 +0000 (11:57 -0700)
committerTom Tromey <tom@tromey.com>
Thu, 3 Jan 2019 21:49:18 +0000 (14:49 -0700)
commitea41325b7d134e91648e340d8297e8f6ee5fe26a
tree204348dde5241942e5ec083ab0d042e84c6d56bf
parent2a3c71d68d452bb6b06d199d0eb7bc0cbc2b9b25
Simplify gdbpy_stop_recording

This simplifies gdbpy_stop_recording, by having it use Py_RETURN_NONE
rather than writing it out manually, and by usin the idiomatic
GDB_PY_HANDLE_EXCEPTION.

gdb/ChangeLog
2019-01-03  Tom Tromey  <tom@tromey.com>

* python/py-record.c (gdbpy_stop_recording): Use Py_RETURN_NONE.
gdb/ChangeLog
gdb/python/py-record.c