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.
This commit is contained in:
parent
492d29ea1c
commit
6c63c96a22
7 changed files with 52 additions and 33 deletions
|
@ -503,15 +503,16 @@ bppy_get_commands (PyObject *self, void *closure)
|
|||
{
|
||||
print_command_lines (current_uiout, breakpoint_commands (bp), 0);
|
||||
}
|
||||
ui_out_redirect (current_uiout, NULL);
|
||||
CATCH (except, RETURN_MASK_ALL)
|
||||
{
|
||||
ui_out_redirect (current_uiout, NULL);
|
||||
do_cleanups (chain);
|
||||
gdbpy_convert_exception (except);
|
||||
return NULL;
|
||||
}
|
||||
END_CATCH
|
||||
|
||||
ui_out_redirect (current_uiout, NULL);
|
||||
cmdstr = ui_file_xstrdup (string_file, &length);
|
||||
make_cleanup (xfree, cmdstr);
|
||||
result = PyString_Decode (cmdstr, strlen (cmdstr), host_charset (), NULL);
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue