From: Fernando Nasser <fnasser@redhat.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: maint set|show internal-error|internal-warning quit|corefile yes|no|auto
Date: Thu, 15 Aug 2002 14:59:00 -0000 [thread overview]
Message-ID: <3D5C2431.D358141@redhat.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2002-08-15 21:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-15 14:51 Andrew Cagney
2002-08-15 14:59 ` Fernando Nasser [this message]
2002-08-16 6:22 ` Carlos O'Donell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D5C2431.D358141@redhat.com \
--to=fnasser@redhat.com \
--cc=ac131313@ges.redhat.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox