From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28594 invoked by alias); 15 Aug 2002 21:59:19 -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 28547 invoked from network); 15 Aug 2002 21:59:19 -0000 Received: from unknown (HELO touchme.toronto.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 15 Aug 2002 21:59:19 -0000 Received: from redhat.com (totem.toronto.redhat.com [172.16.14.242]) by touchme.toronto.redhat.com (Postfix) with ESMTP id 933ACB8050; Thu, 15 Aug 2002 17:59:18 -0400 (EDT) Message-ID: <3D5C2431.D358141@redhat.com> Date: Thu, 15 Aug 2002 14:59:00 -0000 From: Fernando Nasser Organization: Red Hat , Inc. - Toronto X-Accept-Language: en MIME-Version: 1.0 To: Andrew Cagney Cc: gdb@sources.redhat.com Subject: Re: maint set|show internal-error|internal-warning quit|corefile yes|no|auto References: <3D5C225E.4010209@ges.redhat.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-08/txt/msg00167.txt.bz2 I find this useful. At least, it will not hurt to have around. Users are not forced to use it -- they would do it at their own risk ;-) Fernando Andrew Cagney wrote: > > 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 -- Fernando Nasser Red Hat - Toronto E-Mail: fnasser@redhat.com 2323 Yonge Street, Suite #300 Toronto, Ontario M4P 2C9