From: "Martin M. Hunt" <hunt@redhat.com>
To: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: [patch] catch errors restoring breakpoints
Date: Tue, 04 Feb 2003 07:17:00 -0000 [thread overview]
Message-ID: <1044343059.2679.4.camel@Dragon> (raw)
[-- Attachment #1: Type: text/plain, Size: 270 bytes --]
In rare cases, session breakpoints cannot be restored because sources
changed or symbols are not yet loaded. Instead of displaying a
backtrace, just log the error.
2003-02-03 Martin M. Hunt <hunt@redhat.com>
* library/session.tcl (_recreate_bps): Catch errors.
[-- Attachment #2: p --]
[-- Type: text/x-patch, Size: 671 bytes --]
Index: library/session.tcl
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/library/session.tcl,v
retrieving revision 1.13
diff -u -r1.13 session.tcl
--- library/session.tcl 10 Oct 2002 19:39:28 -0000 1.13
+++ library/session.tcl 4 Feb 2003 07:15:24 -0000
@@ -122,7 +122,9 @@
lassign $spec create enabled condition commands
# Create the breakpoint
- gdb_cmd $create
+ if {[catch {gdb_cmd $create} txt]} {
+ dbug W $txt
+ }
# Below we use `\$bpnum'. This means we don't have to figure out
# the number of the breakpoint when doing further manipulations.
reply other threads:[~2003-02-04 7: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=1044343059.2679.4.camel@Dragon \
--to=hunt@redhat.com \
--cc=insight@sources.redhat.com \
/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: link
Be 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).