From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.5-pre1
Date: 16 Aug 93 12:22:44 GMT
From: news.crd.ge.com!e7sa!groleau@uunet.uu.net  (Wes Groleau x1240 C73-8)
Subject: Re: Exceptions in Declarative Region
Message-ID: <CBuqDw.M03@crdnns.crd.ge.com>
List-Id: <comp.lang.ada>

In article <1993Aug13.024920.22726@scf.loral.com> bashford@srs.loral.com (Dave 
Bashford) writes:
>If an exception occurs in the elaboration of a global package or the 
>declaritive part of a main subprogram, there doesn't appear to be any
>way for the program to catch the exception and the user will get the
>cryptic and probably useless error message generated by the Ada runtime
>kernal. Is this true or am I missing something ?

It's true.  However, if that is unacceptable, and if your interactive debugger
doesn't help, try this:

with MAIN_PROGRAM;
procedure EXCEPTION_HANDLER is
  -- nothing here to raise an exception...
begin
   MAIN_PROGRAM;
exception
   when -- you fill in the rest
end EXCEPTION_HANDLER;