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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,baccc6feaf925aec
X-Google-Attributes: gid103376,public
From: "Thierry Lelegard" <lelegard@club-internet.fr>
Subject: Re: PROGRAM_ERROR / Zone corrupted on NEW
Date: 2000/01/02
Message-ID: <84ogcv$ovv$1@front7.grolier.fr>#1/1
X-Deja-AN: 567525357
Content-Transfer-Encoding: 7bit
References: <386a6af9.4993959@news.netvision.net.il>
 <1999Dec29.173827.1@eisner>
X-Priority: 3
Content-Type: text/plain; charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
X-Trace: front7.grolier.fr 946848991 25599 213.44.40.184 (2 Jan 2000 21:36:31
 GMT)
Organization: Club-Internet (France)
X-MSMail-Priority: Normal
Mime-Version: 1.0
NNTP-Posting-Date: 2 Jan 2000 21:36:31 GMT
Newsgroups: comp.lang.ada
Date: 2000-01-02T21:36:31+00:00
List-Id: <comp.lang.ada>

Each time I saw that kind of problem on OpenVMS, it was a
"double deallocation" issue. This is an application error.

Example:

A := new Something;
B := A;
Free (A);
Free (B); -- at this point the zone gets corrupted

After that, I have seen many different kinds of behavior.
This does not mean that the specific datum you mentioned
is the culprit. It may be any other in the same zone
("collection" in Ada words).

Since you are on OpenVMS, I suggest that you use the
"heap analyzer" (see the VMS debugger manual). This
is a brilliant tool.

-Thierry
________________________________________________________
Thierry Lelegard, Paris, France
E-mail: lelegard@club-internet.fr