From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16577 invoked by alias); 15 Aug 2002 21:51:29 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 16529 invoked from network); 15 Aug 2002 21:51:29 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 15 Aug 2002 21:51:29 -0000 Received: from ges.redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 08F733C82 for ; Thu, 15 Aug 2002 17:51:27 -0400 (EDT) Message-ID: <3D5C225E.4010209@ges.redhat.com> Date: Thu, 15 Aug 2002 14:51:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020810 X-Accept-Language: en-us, en MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: maint set|show internal-error|internal-warning quit|corefile yes|no|auto Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-08/txt/msg00166.txt.bz2 Hello, I'd like to propose some new set show options: maint set|show internal-error|internal-warning quit|corefile yes|no|auto When GDB reports an internal problem (error or warning) it gives the user the oportunity to either: - quit GDB - drop a core file The above would let the user override the default (auto) of prompting the user. The user could specify that GDB should always/never quit / drop a core file (mutter something about giving the user too much rope :-). Rationale: I think users have encountered situtations where, while GDB is constantly reporting internal errors or warnings, it is otherwize useable. This, I believe, most often occures in the symbol table reader where recovery is often possible. Letting the user override the internal error/warning behavour would let them at least use GDB. The converse (quit, dump core) is also useful. The current testsuite tends to hang when GDB detects an internal error and tries to prompt for what to do next :-( thoughts? Andrew