public inbox for archer-commits@sourceware.org help / color / mirror / Atom feed
From: pmuldoon@sourceware.org To: archer-commits@sourceware.org Subject: [SCM] archer-pmuldoon-exception-rewind: Only cleanup breakpoint if it was created. Date: Wed, 22 Oct 2008 16:17:00 -0000 [thread overview] Message-ID: <20081022161747.23163.qmail@sourceware.org> (raw) The branch, archer-pmuldoon-exception-rewind has been updated via 537fb5a0965f39d439bba69275191463e041118b (commit) from 13774f62ebfc5012886fed8b10f42d2eca0cdcf6 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email. - Log ----------------------------------------------------------------- commit 537fb5a0965f39d439bba69275191463e041118b Author: Phil Muldoon <pmuldoon@redhat.com> Date: Wed Oct 22 17:17:16 2008 +0100 Only cleanup breakpoint if it was created. ----------------------------------------------------------------------- Summary of changes: gdb/infcall.c | 10 ++++++---- 1 files changed, 6 insertions(+), 4 deletions(-) First 500 lines of diff: diff --git a/gdb/infcall.c b/gdb/infcall.c index 5749d20..ece57ba 100644 --- a/gdb/infcall.c +++ b/gdb/infcall.c @@ -691,10 +691,12 @@ call_function_by_hand (struct value *function, int nargs, struct value **args) if (unwind_on_terminating_exception_p) { tm = lookup_minimal_symbol ("std::terminate()", NULL, NULL); - if (tm != NULL) - terminate_bp = set_momentary_breakpoint_at_pc - (SYMBOL_VALUE_ADDRESS (tm), bp_breakpoint); - make_cleanup_delete_breakpoint (terminate_bp); + if (tm != NULL) + { + terminate_bp = set_momentary_breakpoint_at_pc + (SYMBOL_VALUE_ADDRESS (tm), bp_breakpoint); + make_cleanup_delete_breakpoint (terminate_bp); + } } /* Execute a "stack dummy", a piece of code stored in the stack by hooks/post-receive -- Repository for Project Archer.
reply other threads:[~2008-10-22 16:17 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20081022161747.23163.qmail@sourceware.org \ --to=pmuldoon@sourceware.org \ --cc=archer-commits@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).