From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: ac131313@ges.redhat.com
Cc: carlos@baldric.uwo.ca, gdb@sources.redhat.com
Subject: Re: Issue an internal warning on first deprecated function call
Date: Sun, 18 Aug 2002 11:35:00 -0000 [thread overview]
Message-ID: <9003-Sun18Aug2002213705+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <3D5D030F.4050409@ges.redhat.com> (message from Andrew Cagney on Fri, 16 Aug 2002 09:50:07 -0400)
> Date: Fri, 16 Aug 2002 09:50:07 -0400
> From: Andrew Cagney <ac131313@ges.redhat.com>
>
> (gdb) maint internal-error
> /home/scratch/GDB/src/gdb/maint.c:121: gdb-internal-error: internal
> maintenance
> An internal GDB error was detected. This may make further
> debugging unreliable. Quit this debugging session? (y or n) n
>
> Create a core file containing the current state of GDB? (y or n) n
> (gdb)
>
> s/error/warning/
>
> Since the user is going to need to interact with this, they will get
> very annoyed with it pretty quick.
Yes, I think users will get annoyed and even scared. The message is
meant for the port maintainers, not for users.
> This is why I'm also proposing another command for gaging it :-)
But that won't help, since most users will wtill see the message
until they gag it.
I like Kevin's suggestion better.
next prev parent reply other threads:[~2002-08-18 18:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-15 15:01 Andrew Cagney
2002-08-15 15:33 ` Kevin Buettner
2002-08-15 18:14 ` Daniel Jacobowitz
2002-08-15 18:36 ` Andrew Cagney
2002-08-16 6:31 ` Carlos O'Donell
2002-08-16 6:50 ` Andrew Cagney
2002-08-16 7:09 ` Carlos O'Donell
2002-08-16 7:16 ` Andrew Cagney
2002-08-18 11:35 ` Eli Zaretskii [this message]
2002-08-19 18:23 ` Andrew Cagney
2002-08-20 6:19 ` Carlos O'Donell
2002-08-20 23:36 ` Eli Zaretskii
2002-08-21 6:07 ` Carlos O'Donell
2002-08-21 8:21 ` Andrew Cagney
2002-08-21 8:52 ` Kevin Buettner
2002-08-21 9:29 ` Andrew Cagney
2002-08-22 0:49 ` Eli Zaretskii
2002-08-22 5:43 ` Carlos O'Donell
2002-08-21 10:09 ` Tom Tromey
2002-09-09 11:10 ` Andrew Cagney
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=9003-Sun18Aug2002213705+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=ac131313@ges.redhat.com \
--cc=carlos@baldric.uwo.ca \
--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