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=-0.3 required=5.0 tests=BAYES_00,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,a575249b5f286bfe
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.68.129.169 with SMTP id nx9mr2913025pbb.2.1334347587511;
        Fri, 13 Apr 2012 13:06:27 -0700 (PDT)
Path: 
 r9ni52684pbh.0!nntp.google.com!news2.google.com!npeer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!nntp.club.cc.cmu.edu!feeder.erje.net!news.mixmin.net!aioe.org!.POSTED!not-for-mail
From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Newsgroups: comp.lang.ada
Subject: Re: Garbage Collection ???
Date: Fri, 13 Apr 2012 22:06:17 +0200
Organization: cbb software GmbH
Message-ID: <1ueoh3nw8oobm$.1ww19ebcvg7v4$.dlg@40tude.net>
References: <4f881910$0$2652$703f8584@news.kpn.nl>
 <5o86o2smbjpz.17l849bmku28v$.dlg@40tude.net>
 <4f888010$0$2641$703f8584@news.kpn.nl>
Reply-To: mailbox@dmitry-kazakov.de
NNTP-Posting-Host: Gbl624r6iuNIccy3ASy5ag.user.speranza.aioe.org
Mime-Version: 1.0
X-Complaints-To: abuse@aioe.org
User-Agent: 40tude_Dialog/2.0.15.1
X-Notice: Filtered by postfilter v. 0.8.2
X-Received-Bytes: 1813
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Date: 2012-04-13T22:06:17+02:00
List-Id: <comp.lang.ada>

On Fri, 13 Apr 2012 21:27:23 +0200, ldries46 wrote:

> I have been trying to find the place where a faulty pointer could have been 
> introduced and I come to the conclusion that the return of a procedure in 
> the place.

Note that pointers are most likely passed by value. This means that the way
you are debugging it does not make much sense. Furthermore, dangling
pointers usually manifest themselves after corrupting the program state
beyond any recognition. Thus the observed effect is a consequence of a bug
many source lines and executed instructions away.

You may try to use the GNAT Debug Pool to locate the problem:

http://gcc.gnu.org/onlinedocs/gnat_ugn_unw/The-GNAT-Debug-Pool-Facility.html

Or you may trace all allocations, deallocations, dereferences of the
pointer type. Put the trace into a DB or Excel, sort it by the address key
in order to determine the first place where some pointer gets dangled.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de