From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 725 invoked by alias); 13 Nov 2001 20:38:17 -0000 Mailing-List: contact gdb-help@sourceware.cygnus.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 700 invoked from network); 13 Nov 2001 20:38:15 -0000 Received: from unknown (HELO cygnus.com) (205.180.230.5) by sourceware.cygnus.com with SMTP; 13 Nov 2001 20:38:15 -0000 Received: from theotherone (taarna.cygnus.com [205.180.230.102]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id MAA13556 for ; Tue, 13 Nov 2001 12:38:11 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by theotherone (Postfix) with ESMTP id DC307171F76 for ; Tue, 13 Nov 2001 12:32:02 -0800 (PST) Date: Fri, 02 Nov 2001 06:11:00 -0000 From: Don Howard X-X-Sender: To: Subject: error-catching mechanism for scripts Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2001-11/txt/msg00037.txt.bz2 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