comp.lang.idl-pvwave archive: archive » One RETALL is not enough

Home » Public Forums » archive » One RETALL is not enough

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

One RETALL is not enough [message #81888]

Fri, 26 October 2012 13:26

wlandsman
Messages: 743
Registered: June 2000

Senior Member

While debugging a program, I've been getting error messages after a RETALL like the following:

IDL> retall
% Invalid pointer: <POINTER (<PtrHeapVar2858>)>.
% Execution halted at: XYZ_DEFAULTS::CLEANUP 456
IDL> retall
% Invalid pointer: <POINTER (<PtrHeapVar2578>)>.
% Execution halted at: XYZ_DEFAULTS::CLEANUP 456
IDL> retall
% Temporary variables are still checked out - cleaning up...
IDL> retall

So one RETALL is not enough to get a normal return , but if I give four RETALLs then there is enough of an extra "push" to give a normal return ;-) I first thought this was just a timing problem, and that the pointer cleanup wasn't complete at the time of the first RETALL, but it was complete by the time of the fourth RETALL. But the errors always appear in the same pattern as above, requiring 4 RETALLs no matter how much time I give. Any suggestions as to what is happening? Thanks, --Wayne

P.S. Line 456 where the first errors occurs is the following.

IF OBJ_VALID(self.files.class.Revclasshash) THEN OBJ_DESTROY, self.files.class.Revclasshash

where 'files' and 'class' are structures, and Revclasshash is an object

Report message to a moderator

[Message index]

		One RETALL is not enough By: wlandsman on Fri, 26 October 2012 13:26
		Re: One RETALL is not enough By: Yngvar Larsen on Fri, 02 November 2012 01:13
		Re: One RETALL is not enough By: David Fanning on Thu, 01 November 2012 21:33
		Re: One RETALL is not enough By: Jim Pendleton on Thu, 01 November 2012 20:41

Previous Topic:	Re: cgColor and Widget_Draw Frame problem
Next Topic:	Reading Analog input from IDL

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Oct 08 15:20:01 PDT 2025

Total time taken to generate the page: 0.00262 seconds