From: porton@ex-code.com (Victor Porton)
Subject: Re: use JGNAT for memory debugging?
Date: Wed, 05 Feb 2003 18:53:07 +0500
Date: 2003-02-05T14:17:01+00:00 [thread overview]
Message-ID: <3e411cdd$0$351$bed64819@news.gradwell.net> (raw)
In-Reply-To: 3e40b4ae$0$344$bed64819@news.gradwell.net
In article <4d70a.174206$rM2.163404@rwcrnsc53>,
"Jeffrey Creem" <jeff@thecreems.com> 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.
next prev parent reply other threads:[~2003-02-05 13:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 6:51 Idea: use JGNAT for memory debugging? Victor Porton
2003-02-05 10:32 ` Colin Paul Gloster
2003-02-05 12:12 ` Jeffrey Creem
2003-02-05 13:53 ` Victor Porton [this message]
2003-02-05 15:49 ` Idea: " Florian Weimer
2003-02-05 18:48 ` Stephen Leake
2003-02-06 2:00 ` Victor Porton
2003-02-07 18:22 ` Jean-Claude Mahieux
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox