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,631686271a29a357 X-Google-Attributes: gid103376,public From: "Theodore E. Dennison" Subject: Re: Common Error/Exception Handler Date: 1996/05/04 Message-ID: <318BBAF4.41C67EA6@escmail.orl.mmc.com>#1/1 X-Deja-AN: 153010998 references: <4mg905$9ll@newsbf02.news.aol.com> content-type: text/plain; charset=us-ascii organization: Lockheed Martin Information Systems mime-version: 1.0 newsgroups: comp.lang.ada x-mailer: Mozilla 2.0 (X11; I; SunOS 4.1.3_U1 sun4m) Date: 1996-05-04T00:00:00+00:00 List-Id: LJMetzger wrote: > > On 24 Apr 1996 14:51:25 GMT > gauthier@unilim.fr (Michel Gauthier) wrote: > >FUNDAMENTAL QUESTION : > >is tracing of exceptions really useful ? > > IMHO, it is a valuable tool used to reduce the > "mean time to diagnose" an unwanted feature. The VAX/Ada compiler had a feature where any fatal runtime error produced a full stack dump, including code block labels and line numbers, if run under the debugger. (This "feature" may have actually been a DEC debugger script. Anyway,...) I know of at least one major (NASA-sponsored) project that considered this feature so vital, that all of the delivered code (including real-time stuff) was to be run under the DEC debugger. They had (have) very stringent yearly downtime limits written into the contract, so it was considered vital to be able to track down any problems as quickly as possible. To be honest, I'm suprised more compilers or linkers don't offer an option to produce a stack dump (although core dumps can be pretty useful too). -- T.E.D. | Work - mailto:dennison@escmail.orl.mmc.com | | Home - mailto:dennison@iag.net | | URL - http://www.iag.net/~dennison |