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,start X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-04-26 02:51:25 PST Path: newsfeed.google.com!newsfeed.stanford.edu!news.tele.dk!130.133.1.3!fu-berlin.de!bolzen.all.de!news1.transmedia.de!news-FFM2.ecrc.net!news.siemens.de!news.mch.sbs.de!not-for-mail From: Alfred Hilscher Newsgroups: comp.lang.ada Subject: Postmortem debugging with ada ? Date: Thu, 26 Apr 2001 11:51:00 +0200 Organization: Siemens AG Message-ID: <3AE7EF84.9157A90C@icn.siemens.de> NNTP-Posting-Host: 139.21.122.158 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en Xref: newsfeed.google.com comp.lang.ada:6947 Date: 2001-04-26T11:51:00+02:00 List-Id: 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) ?