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-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 nx9mr3286210pbb.2.1334357384122;
        Fri, 13 Apr 2012 15:49:44 -0700 (PDT)
Path: 
 r9ni53101pbh.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!newsfeed.straub-nv.de!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail
From: Brian Drummond <brian@shapes.demon.co.uk>
Newsgroups: comp.lang.ada
Subject: Re: Garbage Collection ???
Date: Fri, 13 Apr 2012 22:49:40 +0000 (UTC)
Organization: A noiseless patient Spider
Message-ID: <jmaai4$aga$1@dont-email.me>
References: <4f881910$0$2652$703f8584@news.kpn.nl>
	<5o86o2smbjpz.17l849bmku28v$.dlg@40tude.net>
	<4f888010$0$2641$703f8584@news.kpn.nl>
Mime-Version: 1.0
Injection-Date: Fri, 13 Apr 2012 22:49:40 +0000 (UTC)
Injection-Info: mx04.eternal-september.org;
 posting-host="DkTdSjxOCm6DqG+Uf7eArg";
	logging-data="10762"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX198DZYMD0uHMdLmt8OCtxDRsJ91wziMhZ0="
User-Agent: Pan/0.135 (Tomorrow I'll Wake Up and Scald Myself with Tea; GIT
	30dc37b master)
Cancel-Lock: sha1:RkhUxj2LBD7pwEqCHVEbKN0BlCY=
X-Received-Bytes: 1701
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Date: 2012-04-13T22:49:40+00: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.
> I did position some variables (edge_debug1 till edge_debug4) to be
> filled with the value of the original pointer at various places 

I would declare these variables as not null access whatever, to get an 
exception on assignment to them, rather than waiting until the error 
manifests as a segv. (Do you have a lot of checks turned off, so that it 
doesn't raise Storage_Error)?

- Brian