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
X-Google-Thread: 103376,33fb44bd15dd424a,start
X-Google-Attributes: gid103376,public
From: =?iso-8859-1?Q?Joachim_Schr=F6er?= <schroeer@S1333.AMST.CO.AT>
Subject: Exception stack trace from DLL's
Date: 1998/06/09
Message-ID: <01BD93B5.31CCA220@prg08>#1/1
X-Deja-AN: 361014198
Sender: Ada programming language <INFO-ADA@LISTSERV.NODAK.EDU>
Content-Transfer-Encoding: quoted-printable
Comments: cc: Recipients of INFO-ADA digests
 <LISTSERV.NODAK.EDU!INFO-ADA@s1333.amst.co.at>
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Date: 1998-06-09T00:00:00+00:00
List-Id: <comp.lang.ada>


Hello,=20

I call subprograms from DLL's build with ObjectAda 7.1.1 from a C-main.
When exceptions are raised in those subprograms, the stack-trace=20
only gives addresses. I had the same problem when first working with=20
windows-programs (instead of DOS-console programs). But here I
was able to solve the problem by calling a pop-up window and feeding
it with Ada.Exceptions.Exception_Information. The complete symbolic=20
information with line-numbers and package-names was in there.
Not so when working with DLL's.=20

Has anyone an idea?

J. Schr=F6er