From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cagney To: gdb@sources.redhat.com Subject: Should internal-error default to dumping core? Date: Mon, 01 Oct 2001 08:01:00 -0000 Message-id: <3BB88526.8050809@cygnus.com> X-SW-Source: 2001-10/msg00004.html 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