]> git.ipfire.org Git - thirdparty/binutils-gdb.git/commit
Remove 'if' from GDB_PY_HANDLE_EXCEPTION
authorTom Tromey <tom@tromey.com>
Fri, 22 Dec 2023 18:43:26 +0000 (11:43 -0700)
committerTom Tromey <tom@tromey.com>
Thu, 14 Mar 2024 14:57:00 +0000 (08:57 -0600)
commitb0e7d28eae1fa1a91932e47d8cf5decf96c2bc59
tree91e5771f2592527303d2fcfc38dc3a87cb738f07
parent9a03f2185347bd8f20da9bf535bc68a8d0f18ce8
Remove 'if' from GDB_PY_HANDLE_EXCEPTION

This removes the embedded 'if' from GDB_PY_HANDLE_EXCEPTION and
GDB_PY_SET_HANDLE_EXCEPTION.  I believe this 'if' was necessary with
the old gdb try/catch macros, but it no longer is: these should only
ever be called from a 'catch' block, where it's already known that an
exception was thrown.

Simon pointed out, though, that in a few spots, these were in facts
called outside of 'catch' blocks.  This patch cleans up these spots.
I also found one spot where a redundant 'return nullptr' could be
removed.
gdb/python/py-breakpoint.c
gdb/python/py-inferior.c
gdb/python/py-infthread.c
gdb/python/py-value.c
gdb/python/python-internal.h