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,6ac8f960b3e80ee1 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-02-05 06:17:02 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!lon1-news.nildram.net!news-peer.gradwell.net!not-for-mail Newsgroups: comp.lang.ada From: porton@ex-code.com (Victor Porton) Date: Wed, 05 Feb 2003 18:53:07 +0500 References: <3e40b4ae$0$344$bed64819@news.gradwell.net> Organization: Extreme Code Software (http://ex-code.com) Subject: Re: use JGNAT for memory debugging? Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Content-Type: text/plain; charset=us-ascii X-URL: http://www.ex-code.com/ Message-ID: <3e411cdd$0$351$bed64819@news.gradwell.net> NNTP-Posting-Date: 05 Feb 2003 14:17:01 GMT NNTP-Posting-Host: 195.149.39.13 X-Trace: 1044454621 news.gradwell.net 351 mail2news/195.149.39.13 X-Complaints-To: news-abuse@gradwell.net Xref: archiver1.google.com comp.lang.ada:33811 Date: 2003-02-05T14:17:01+00:00 List-Id: In article <4d70a.174206$rM2.163404@rwcrnsc53>, "Jeffrey Creem" writes: > Perhaps gnatmem can help (not entirely clear what you are seeing) > > Also, make sure you are building with all run-time checks enabled (gnato and > fstack-check) > > Finally, take a look at the section of that GNAT User's Guide titled > > Finding Memory Problems with GNAT Debug Pool Already all of this. These may not find the cases of accessing dangling references.