This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: maint set|show internal-error|internal-warning quit|corefile yes|no|auto
- From: Fernando Nasser <fnasser at redhat dot com>
- To: Andrew Cagney <ac131313 at ges dot redhat dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Thu, 15 Aug 2002 17:59:13 -0400
- Subject: Re: maint set|show internal-error|internal-warning quit|corefile yes|no|auto
- Organization: Red Hat , Inc. - Toronto
- References: <3D5C225E.4010209@ges.redhat.com>
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