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.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII
X-Google-Thread: 103376,ded9cd74b22b548d
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2001-04-26 04:56:43 PST
Message-ID: <3AE80B95.D879F930@amsjv.com>
Date: Thu, 26 Apr 2001 12:50:45 +0100
From: Des Walker <des.walker@amsjv.com>
Organization: Alenia-Marconi Systems
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: Postmortem debugging with ada ?
References: <3AE7EF84.9157A90C@icn.siemens.de> <3AE7FE5A.C70D9590@nbi.dk>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
NNTP-Posting-Host: farwkn6911.frlngtn.gecm.com
X-Trace: 26 Apr 2001 12:44:39 GMT, farwkn6911.frlngtn.gecm.com
Path: 
 newsfeed.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!btnet-peer1!btnet-feed5!btnet!newreader.ukcore.bt.net!pull.gecm.com!farwkn6911.frlngtn.gecm.com
Xref: newsfeed.google.com comp.lang.ada:6949
Date: 2001-04-26T12:50:45+01:00
List-Id: <comp.lang.ada>

Jacob Sparre Andersen wrote:
> 
> Alfred:
> 
> > Is there a similar way with GNAT or Aonix (e.g. in case of
> > constraint_error) ?
> 
> On Unix-like systems you are generally able to get a "core dump"
> from a crashed program. GVD should be able to load this so you
> can inspect it.
> 
> I know that debuggers can introduce/remove errors not found in
> the wild, but have you considered running the program inside a
> debugger, before you try using core dumps?
> 
> Jacob (who hasn't looked at core dumps for years)
> --
> Harddiske er bin�re enheder: Enten er de nye, eller ogs� er de fyldt op.

Hi,

we've used gdb to analyse core files from Ada (compiled with GNAT and -g
switch) for a few years now. This worked fine, even with high levels of
code optimisation, with the startup location being the point at which
the unhandled exception was raised. It was easy to check the thread
stack to get the context.

Applications were running on SPARC under Solaris 2.5.x and 2.6, and also
on Pentium under Linux.

When running the application under the debugger control (gdb), we found
it best to trap exceptions by breaking on __gnat_raise. But as I can't
recall why, that may not be relevant :)

	HTH
	Des Walker
	Alenia-Marconi Systems