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=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,8de5e9f508817948
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 1994-10-23 12:14:45 PST
Path: 
 bga.com!news.sprintlink.net!howland.reston.ans.net!gatech!paladin.american.edu!auvm!J64.STRATCOM.AF.MIL!BennettC
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: comp.lang.ada
Encoding: 50 TEXT
X-Mailer: Microsoft Mail V3.0
Message-ID: <2EA6BEBD@SMTPGATE2.STRATCOM.AF.MIL>
Date: Thu, 20 Oct 1994 12:10:00 PDT
Sender: Ada programming language <INFO-ADA@NDSUVM1.BITNET>
From: "Bennett, Chip (KTR) ~U" <BennettC@J64.STRATCOM.AF.MIL>
Subject: Re: Verdix Exception Traceback history
Date: 1994-10-20T12:10:00-07:00
List-Id: <comp.lang.ada>

> >My company is currently evaluating the Verdix compile
> >on Sun platform.  One problem we have run into is
> >that when an exception is raised the only traceback
> >history that is printed is
> >
> >  Main Program Abandon Exception ________
> >
> >Other compilers I have used provided a text description
> >of all the subprograms and line numbers the exception
> >was propergated thru.
> >
> >How do I get the Verdix compiler to do this?
> >
> >
> >Walt Barnes  Software Engineer
>
> ...
> ...
>
> A SECOND SOLUTION:
>
> The call stack can be viewed using the core dump file. The
> Verdix/Rational Ada debugger version I am using (version 1.1) does not
> work with core dumps (I hear that future versions will/do).  Instead
> the dbx tool can be used to view the Ada call stack. To use dbx with a
> core file follow the steps below.
>
>   1) Attach the exception handler as shown in the example below.
>   2) Change the core file size limit in your .cshrc file.
>
>        limit coredumpsize 10000
>
>   3) Run program and recreate exception.  A core file will be created.
>   4) Run dbx debugger in directory of the core and executable files.
>
>        dbx <executable name>
>
>   5) Type the dbx command RwhereS to see the call stack trace back.

Am I missing something here?  If re-running the program is an option, you
don't need a core dump.  Just run the program under a.db until you get the
exception, and use the "cs" subcommand to print out the call stack.

*****************************************************************
* Chip Bennett                  | BennettC@j64.stratcom.af.mil  *
* USSTRATCOM/J64213             | Voice (402)294-7360           *
* 901 SAC Blvd, Suite 2B24      | FAX   (402)294-7912           *
* Offutt AFB, NE 68113-6600     |                               *
*****************************************************************