From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,cacf2a126e0a3921
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: GNAT 3.10p OS/2 Assert/Library bug?
Date: 1997/10/27
Message-ID: <dewar.877991079@merv>#1/1
X-Deja-AN: 285388552
References: <swhalenEIpFIC.MB0@netcom.com>
X-Complaints-To: usenet@news.nyu.edu
X-Trace: news.nyu.edu 877991134 6613 (None) 128.122.140.58
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1997-10-27T00:00:00+00:00
List-Id: <comp.lang.ada>


Steve Whalen asks

<<If there is any way I can look up this bug in ACT's bug list myself to
  see if they already know about it, please let me know because I'd be
  happy to do that. But so far I haven't figured out a way to do so (and
  haven't seen this particular bug mentioned on CLA or on GNAT / Chat).>>

We do not publish such a list. A major reason for not publishing it is
that our experience is that in virtually 100% of cases, when people think
they have a bug that is the same as one in the list, they are wrong. The
trouble is that many bugs correspond to very special sets of circumstances,
and of course you don't know what these are before you fix it (often you
don't even know after you fixed it). So the attempt to identify a bug with
something on the list *does* waste time, both for the submitter and for
us (since it is almost never useful).

<<If it's NOT possible for me to look this up in ACT's bug list, then I
  would like to get input from the folks on CLA regarding what appears
  to be a bug in GNAT 3.10p for OS/2 - emx (and also GNAT 3.07 for MsDos
  - DJGPP) (but which is NOT visible in GNAT 3.10p Linux, etc.).  I
  don't want to report it if it's already known, because I presume it
  would take ACT "some" amount of time to figure out they already know
  about it, or it's already fixed in an upcoming release, etc.>>

You should report it. Only we can tell if it's already known, and often
even we won't be able to see that it is related to another bug. We are
happy to get bug reports from unsupported users, and we certainly do not
regard such reports as a waste of time. Eventually all such reports are
looked at, and one encouraging aspect of GNAT is that even as the number
of users is going up, the number of open bug reports is steadily 
decreasing, including those reported by unsupported users.

What you are more likely to do if you post GNAT bug reports on CLA is
to waste the time of CLA readers, virtually none of whom are going to
take the time to examine a bug report of this kind. If you think you
have a bug report, send it along to report@gnat.com!

Note that we never take bug reports from CLA, there is no easy way for
us to do this, so please forward this report to the proper address.

Robert Dewar
Ada Core Technologies