From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9468 invoked by alias); 13 Jan 2002 20:22:32 -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 9435 invoked from network); 13 Jan 2002 20:22:31 -0000 Received: from unknown (HELO localhost.cygnus.com) (24.114.42.213) by sources.redhat.com with SMTP; 13 Jan 2002 20:22:31 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.cygnus.com (Postfix) with ESMTP id 934833D1F; Sun, 13 Jan 2002 15:22:29 -0500 (EST) Message-ID: <3C41EC85.5000302@cygnus.com> Date: Sun, 13 Jan 2002 12:22:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.7) Gecko/20020103 X-Accept-Language: en-us MIME-Version: 1.0 To: Fernando Nasser Cc: gdb@sources.redhat.com Subject: Re: Should internal-error default to dumping core? References: <3BB88526.8050809@cygnus.com> <3BB88AE6.F53EDC5@redhat.com> <3BB89072.6070601@cygnus.com> <3BB893EA.B45050D0@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-01/txt/msg00139.txt.bz2 > Andrew Cagney wrote: > >> >> Sorry you've lost me here. query() returns false if there is no tty. >> So ``n'' ``n'' would still be the default. I'll need to change the >> question so that a ``no'' indicates a core dump. >> > > > That was how I was suggesting it should be, so it is OK with me. > Turns out I'm 180 degrees out here. query() returns true when no TTY. Consequently I need to reverse first query() not the second. Andrew > Hello, > > At preset an internal-error interaction looks like: > > (gdb) maint internal-error > /home/scratch/GDB/src/gdb/maint.c:119: gdb-internal-error: internal maintenance > An internal GDB error was detected. This may make further > debugging unreliable. Continue this debugging session? (y or n) n > > Create a core file containing the current state of GDB? (y or n) n >> $ > > that is the default/no case is to not dump core. > > At present, if GDB encounters an internal error (from say a NULL pointer reference) it doesn't leave any physical evidence around in the form of a core dump. I'm thinking it should. Hence, I'd like to change the second prompt to be one that defaults to a core dump. > > Looking back through the notes it appears that the [my] rationale for the current behavour was somewhat arbitrary. > > thoughts? > Andrew