From: Andrew Haley <aph@cambridge.redhat.com>
To: "Boehm, Hans" <hans_boehm@hp.com>
Cc: "'Mark Wielaard'" <mark@klomp.org>, java@gcc.gnu.org
Subject: RE: Analysis of Mauve failures - The final chapter
Date: Fri, 05 Apr 2002 11:35:00 -0000 [thread overview]
Message-ID: <15533.60046.9658.505927@cuddles.cambridge.redhat.com> (raw)
In-Reply-To: <40700B4C02ABD5119F000090278766443BF174@hplex1.hpl.hp.com>
Thank you for the reminder.
Boehm, Hans writes:
> As it stands, I'm hesitant to turn off the warnings by default, though
> I can see arguments either way. If the warnings occur repeatedly,
> they are indicative of a potential memory leak. If someone wants to
> turn it off by default, and instead provide an environment variable to
> turn it back on, I could probably be talked into that, too.
It seems to me that we have to make up our minds.
IMO: If we are shipping a production-quality system then we shouldn't
output warnings about which we'll say "ah, don't worry about that
message, we already know about that." It doesn't look good, and it
will suggest to people that we don't have a serious offering. This is
especially true if the warning message uses obscure and frightening
terminology. This warning message looks like something major has
failed.
Andrew.
next prev parent reply other threads:[~2002-04-05 18:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 9:27 Boehm, Hans
2002-04-05 11:35 ` Andrew Haley [this message]
2002-04-05 11:41 ` Per Bothner
-- strict thread matches above, loose matches on Subject: below --
2002-04-08 15:20 Boehm, Hans
2002-04-08 13:33 Boehm, Hans
2002-04-05 11:37 Boehm, Hans
2002-04-05 12:16 ` Per Bothner
2002-04-08 13:32 ` Tom Tromey
2002-04-04 16:45 Boehm, Hans
2002-04-04 17:14 ` Mark Wielaard
2002-04-05 3:47 ` Mark Wielaard
2002-04-05 4:07 ` Andrew Haley
2002-04-05 4:22 ` Mark Wielaard
2002-04-08 13:40 ` Tom Tromey
2002-04-08 14:56 ` Mark Wielaard
2002-04-08 17:31 ` Mark Wielaard
2002-04-09 0:49 ` Bryce McKinlay
2002-04-19 19:59 ` Tom Tromey
2002-04-05 1:15 ` Andrew Haley
2002-04-04 7:27 Mark Wielaard
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=15533.60046.9658.505927@cuddles.cambridge.redhat.com \
--to=aph@cambridge.redhat.com \
--cc=hans_boehm@hp.com \
--cc=java@gcc.gnu.org \
--cc=mark@klomp.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).