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-7-bit X-Google-Thread: 103376,ded9cd74b22b548d X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-05-01 10:05:44 PST Path: newsfeed.google.com!newsfeed.stanford.edu!feed.textport.net!hammer.uoregon.edu!skates!not-for-mail From: Stephen Leake Newsgroups: comp.lang.ada Subject: Re: Postmortem debugging with ada ? Date: 01 May 2001 13:03:14 -0400 Organization: NASA Goddard Space Flight Center Message-ID: References: <3AE7EF84.9157A90C@icn.siemens.de> NNTP-Posting-Host: anarres.gsfc.nasa.gov Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: skates.gsfc.nasa.gov 988737512 8171 128.183.220.71 (1 May 2001 17:18:32 GMT) X-Complaints-To: dscoggin@cne-odin.gsfc.nasa.gov NNTP-Posting-Date: 1 May 2001 17:18:32 GMT User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.6 Xref: newsfeed.google.com comp.lang.ada:7070 Date: 2001-05-01T17:18:32+00:00 List-Id: Alfred Hilscher writes: > Hi, > > in my early DOS days I worked with the Logitech Modula-2 compiler. This > tool had a nice feature called postmortem debugging. If a programm > crashes (e.g. due to rangeoverflow, indexunderflow etc.) it produced a > dump file which could be analyzed symbolically. So if a program (with > enabled checkes) failed by some user, he could send this dump file to > the developer and this one then could simple find the location and the > reason by inspecting the call chain and the data. > > Is there a similar way with GNAT or Aonix (e.g. in case of > constraint_error) ? Others have mentioned using gdb with core dumps. Another approach is to output a symbolic stack trace. GNAT provides the package GNAT.Traceback.Symbolic. This allows your users to not have gdb installed; a good feature. -- -- Stephe