|Re: HELP with programming the HP50G|
Message #2 Posted by Vieira, Luiz C. (Brazil) on 28 July 2010, 7:57 p.m.,
in response to message #1 by Namir
the only explanation that comes (at this point, at least) to my mind is that you are storing data in local variables that have been created by instance(s) of the program still HALTed. Please, check if the HLT annunciator is shown in the upper right corner of the display and, if so, use KILL to stop/remove any pending session, hence killing any local variables still active.
I am not sure if there is something else, like storing/retrieving data in a directory chain, but once I had observed such particular memory handling structure while step-by-step executing HP48/49/50 programs, I think yours is the same case.
You see, if you are debugging a program and notice one problem, edit it, correct the problem, store the edited version and go ahead stepping through the halted version, you are actually stepping into the original, unmodified version. If you start a new one without KILLing any pending programs, you have something like a memory leak (described in previous threads... I liked the term!!!): the newly executed program, either in straight execution or in step-by-step mode, does not automatically kill the halted executions, and these program 'ghosts' use memory in a 'hidden' way. You can only go back to previously halted program(s) instances once you go ahead and finish the one(s) halted after those. KILL, however, wipes them all out.
Hope this helps a bit.
Edited: 28 July 2010, 8:06 p.m.