aboutsummaryrefslogtreecommitdiff
path: root/gdb/python/py-breakpoint.c
diff options
context:
space:
mode:
authorAndrew Burgess <aburgess@redhat.com>2022-10-04 14:22:25 +0100
committerAndrew Burgess <aburgess@redhat.com>2022-10-20 16:41:51 +0100
commit705b6305edc025c31606de16623a549697891193 (patch)
treea1802c4e652b7e2e79e13233f6219bdd43f322e2 /gdb/python/py-breakpoint.c
parentb2ff9ed3050491f72529beeea14859abda3afb4a (diff)
downloadbinutils-705b6305edc025c31606de16623a549697891193.zip
binutils-705b6305edc025c31606de16623a549697891193.tar.gz
binutils-705b6305edc025c31606de16623a549697891193.tar.bz2
gdb: used scoped_restore_frame in update_watchpoint
I was doing some int to bool cleanup in update_watchpoint, and I noticed a manual version of scoped_restore_selected_frame. As always when these things are done manually, there is the chance that, in an error case, we might leave the wrong frame selected. This commit updates things to use scoped_restore_selected_frame, and also converts a local variable from int to bool. The only user visible change after this commit is in the case where update_watchpoint throws an error - we should now correctly restore the previously selected frame. Otherwise, this commit should be invisible to the user. Approved-By: Simon Marchi <simon.marchi@efficios.com>
Diffstat (limited to 'gdb/python/py-breakpoint.c')
0 files changed, 0 insertions, 0 deletions