aboutsummaryrefslogtreecommitdiff
path: root/gdb/mi
diff options
context:
space:
mode:
authorPedro Alves <palves@redhat.com>2017-10-04 11:07:28 +0100
committerPedro Alves <palves@redhat.com>2017-10-04 13:01:20 +0100
commit73dcd72d4eeec176f769660ddcdefd1f25d0a2ec (patch)
tree733a256c53bcca16a687a41d1520fafba2f46694 /gdb/mi
parent44704526e482d24baa104764495ca376561a85bf (diff)
downloadgdb-73dcd72d4eeec176f769660ddcdefd1f25d0a2ec.zip
gdb-73dcd72d4eeec176f769660ddcdefd1f25d0a2ec.tar.gz
gdb-73dcd72d4eeec176f769660ddcdefd1f25d0a2ec.tar.bz2
Move code out of 'between TRY and CATCH'
I tried building GDB with TRY/CATCH mapped to raw C++ try/catch (by defining GDB_XCPT to GDB_XCPT_RAW_TRY in gdb/common/common-exceptions.h), and that caught a case of code written between try and catch. This commit fixes it. gdb/ChangeLog: 2017-10-04 Pedro Alves <palves@redhat.com> * guile/scm-breakpoint.c (gdbscm_breakpoint_commands): Move code out of 'between TRY and CATCH'.
Diffstat (limited to 'gdb/mi')
0 files changed, 0 insertions, 0 deletions