From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: ac131313@ges.redhat.com, gdb@sources.redhat.com
Subject: Re: Issue an internal warning on first deprecated function call
Date: Thu, 22 Aug 2002 05:43:00 -0000 [thread overview]
Message-ID: <20020822124031.GB29293@systemhalted> (raw)
In-Reply-To: <2110-Thu22Aug2002105101+0300-eliz@is.elta.co.il>
On Thu, Aug 22, 2002 at 10:51:02AM +0300, Eli Zaretskii wrote:
> > Date: Wed, 21 Aug 2002 09:05:08 -0400
> > From: "Carlos O'Donell" <carlos@baldric.uwo.ca>
> >
> > > > 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.
>
> The warning was being considered for the case when GDB calls a
> deprecated function. As long as the deprecated function does its job,
> a GDB user doesn't care about it being called. We certainly should
> not scare users in this case telling them something like "GDB will
> likely crash in a moment; you HAVE been warned!".
I apologize for finding it hard to track a true line between gdb-user
and gdb-developer ;-)
c.
next prev parent reply other threads:[~2002-08-22 12:43 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
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 [this message]
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=20020822124031.GB29293@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=ac131313@ges.redhat.com \
--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