* Re: PROGRAM_ERROR / Zone corrupted on NEW
1999-12-29 0:00 PROGRAM_ERROR / Zone corrupted on NEW Robert Barron
@ 1999-12-29 0:00 ` Larry Kilgallen
2000-01-02 0:00 ` Thierry Lelegard
0 siblings, 1 reply; 3+ messages in thread
From: Larry Kilgallen @ 1999-12-29 0:00 UTC (permalink / raw)
In article <386a6af9.4993959@news.netvision.net.il>, robert_jm_barron@hotmail.com (Robert Barron) writes:
> If I don't deallocate, there is no problem, except a random accvio at
> some future stage which I haven't found, but blamed on the fact that I
> didn't deallocate the record.
It is extremely unlikely that you would get SS$_ACCVIO because of
a failure to deallocate. My suspicion would be that your program
is trashing memory.
Larry Kilgallen
^ permalink raw reply [flat|nested] 3+ messages in thread
* PROGRAM_ERROR / Zone corrupted on NEW
@ 1999-12-29 0:00 Robert Barron
1999-12-29 0:00 ` Larry Kilgallen
0 siblings, 1 reply; 3+ messages in thread
From: Robert Barron @ 1999-12-29 0:00 UTC (permalink / raw)
Hi,
I've got a problem when allocating a record.
I call a procedure, allocate a record (with NEW), and before exiting
do an UNCHECKED_DEALLOCATION.
The next time I call the procedure, I get a PROGRAM_ERROR exception
(the system message is ZONE CORRUPTED from LIB$GET_VM (this is the VMS
part)
If I don't deallocate, there is no problem, except a random accvio at
some future stage which I haven't found, but blamed on the fact that I
didn't deallocate the record.
However, I got this (consistent) program_error instead.
Does anyone have any Idea?
ADA 3.4-2 (ada 83) on VMS 6.2-h3 (I think 6.2 h something anyway) AXP.
Thanks in advance,
P.S. please answer to the E-mail too, thanx.
``Farming looks easy when your plow is a pencil and you're a thousand miles from a cornfield.'' - Dwight D. Eisenhower
The Barron Family. robert_jm_barron@hotmail.com
The Voyages of the Voyagers :
<http://www.geocities.com/CapeCanaveral/Lab/7284/voyager.htm>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: PROGRAM_ERROR / Zone corrupted on NEW
1999-12-29 0:00 ` Larry Kilgallen
@ 2000-01-02 0:00 ` Thierry Lelegard
0 siblings, 0 replies; 3+ messages in thread
From: Thierry Lelegard @ 2000-01-02 0:00 UTC (permalink / raw)
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2000-01-02 0:00 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-12-29 0:00 PROGRAM_ERROR / Zone corrupted on NEW Robert Barron
1999-12-29 0:00 ` Larry Kilgallen
2000-01-02 0:00 ` Thierry Lelegard
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox