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: bobduff@world.std.com (Robert A Duff)
Subject: Re: Common Error/Exception Handler
Date: 1996/05/10
Message-ID: <Dr7IGt.GxM@world.std.com>#1/1
X-Deja-AN: 154178943
references: <gauthier-2404961547320001@164.81.60.62>
 <JSA.96May9163744@organon.com> <Dr6x9B.5LA@bton.ac.uk>
organization: The World Public Access UNIX, Brookline, MA
newsgroups: comp.lang.ada
Date: 1996-05-10T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <Dr6x9B.5LA@bton.ac.uk>, John English <je@bton.ac.uk> wrote:
>Hmm, I'm starting to confuse myself with versions.  I'm running 3.03
>under Linux and 3.01 under NT at home, 3.01 and 3.03 on the Suns and
>Alphas at work, and 2.07 on the PCs in our student labs.  Since it's
>usually students who come to see me with unhandled exception problems
>(*I* never get into these pickles... :-) that would explain it.  So,
>oops, I stand corrected.  And hopefully in some future version the
>file name and line number will be provided too...

To really get any useful information, you have to go into gdb.  File
name and line number are nice, but you *really* want a stack trace-back.

I'm not a big fan of hacking around in debuggers, but a stack trace-back
seems like a minimal amount of useful information.  For example, I
sometimes have a procedure called Validate(X), which raises an exception
if there's something wrong with X.  I don't just want to know where in
Validate it failed -- I want to know which call to Validate failed.

- Bob