From: Don Howard <dhoward@redhat.com>
To: <gdb@sources.redhat.com>
Subject: error-catching mechanism for scripts
Date: Fri, 02 Nov 2001 06:11:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0111131120520.13411-100000@theotherone> (raw)
I've been trying to find a way to make gdb command scripts handle errors
in a flexible way -- either making continue-on-error an option or some
kind of simple exception catching mechanism:
set script-continue-on-error 1
-- or --
try
commands
catch
commands
end
I'd like to know what others think.
--
-Don
dhoward@redhat.com
gdb engineering
next reply other threads:[~2001-11-13 20:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-02 6:11 Don Howard [this message]
2001-11-02 8:33 ` Andrew Cagney
2001-11-27 8:43 Don Howard
2001-11-17 12:21 ` Don Howard
2001-11-27 20:17 ` Andrew Cagney
2001-11-18 10:57 ` Andrew Cagney
2001-11-19 15:11 ` Fernando Nasser
2001-11-28 6:52 ` Fernando Nasser
2001-11-28 6:57 ` Arnaud Charlet
2001-11-20 8:44 ` Arnaud Charlet
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=Pine.LNX.4.33.0111131120520.13411-100000@theotherone \
--to=dhoward@redhat.com \
--cc=gdb@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