This is the mail archive of the
gdb-testers@sourceware.org
mailing list for the GDB project.
[binutils-gdb] more making TRY/CATCH callers look more like real C++ try/catch blocks
- From: sergiodj+buildbot at redhat dot com
- To: gdb-testers at sourceware dot org
- Date: Sat, 07 Mar 2015 12:56:43 -0500
- Subject: [binutils-gdb] more making TRY/CATCH callers look more like real C++ try/catch blocks
- Authentication-results: sourceware.org; auth=none
*** TEST RESULTS FOR COMMIT 6c63c96a22d216fb5d51c5d93646066d29e08ea1 ***
Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 6c63c96a22d216fb5d51c5d93646066d29e08ea1
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.