From: Andrew Cagney <ac131313@ges.redhat.com>
To: Carlos O'Donell <carlos@baldric.uwo.ca>
Cc: Eli Zaretskii <eliz@is.elta.co.il>, gdb@sources.redhat.com
Subject: Re: Issue an internal warning on first deprecated function call
Date: Wed, 21 Aug 2002 08:21:00 -0000 [thread overview]
Message-ID: <3D63AFF8.30009@ges.redhat.com> (raw)
In-Reply-To: <20020821130508.GC17486@systemhalted>
>> >
>> > What's wrong with making users scared?
>
>>
>> It's wrong because GDB users cannot do anything about the problem, and
>> the message's language seems to imply it's a potentially very grave
>> problem (which it isn't).
>>
>
>
> It's not a grave problem? Please explain.
Eli's right here. The warning would be to strong.
internal-error and internal-warning refer to GDB detecting an errenous
internal state. Error for non-recoverable, warning for recoverable.
Unless some action is taken, the long term prognosis doesn't look good.
However, short term, GDB could just as easily die due to a SIGSEG.
>> > What if there are no port maintainers?
>
>> Then the head maintainer gets the honor.
>
>
> Like the parisc port?
Yep. I get to ``fix'' the problem.
I just checked in a change to MAINTAINERS file so that it recommends
hppa-elf as the target to try building. This new target doesn't include
som support (unlike hppa natives) and so makes the multi-arch task just
that bit more feasible :-)
enjoy,
Andrew
next prev parent reply other threads:[~2002-08-21 15:21 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
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 [this message]
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=3D63AFF8.30009@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=carlos@baldric.uwo.ca \
--cc=eliz@is.elta.co.il \
--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