aboutsummaryrefslogtreecommitdiff
path: root/gdb/arch-utils.h
diff options
context:
space:
mode:
authorPedro Alves <palves@redhat.com>2015-03-07 14:50:05 +0000
committerPedro Alves <palves@redhat.com>2015-03-07 15:19:57 +0000
commit6c63c96a22d216fb5d51c5d93646066d29e08ea1 (patch)
tree310e31afd2f492535ae37445861bc007473180dd /gdb/arch-utils.h
parent492d29ea1c9a8b2c7d5193908119a4e27c045687 (diff)
downloadgdb-6c63c96a22d216fb5d51c5d93646066d29e08ea1.zip
gdb-6c63c96a22d216fb5d51c5d93646066d29e08ea1.tar.gz
gdb-6c63c96a22d216fb5d51c5d93646066d29e08ea1.tar.bz2
more making TRY/CATCH callers look more like real C++ try/catch blocks
All these were caught by actually making TRY/CATCH use try/catch behind the scenes, which then resulted in the build failing (on x86_64 Fedora 20) because there was code between the try and catch blocks. gdb/ChangeLog: 2015-03-07 Pedro Alves <palves@redhat.com> * breakpoint.c (save_breakpoints): Adjust to avoid code between TRY and CATCH. * gdbtypes.c (safe_parse_type): Remove empty line. (types_deeply_equal): * guile/scm-frame.c (gdbscm_frame_name): * linux-thread-db.c (find_new_threads_once): * python/py-breakpoint.c (bppy_get_commands): * record-btrace.c (record_btrace_insert_breakpoint) (record_btrace_remove_breakpoint, record_btrace_start_replaying) (record_btrace_start_replaying): Adjust to avoid code between TRY and CATCH.
Diffstat (limited to 'gdb/arch-utils.h')
0 files changed, 0 insertions, 0 deletions