Operand stack access

Hello,

Up to now, the operand stack is inaccessible par JPDA.

But:

揟he operand stack is empty when the frame that contains it is created.擩VM Specification book

So when a Method entry event occurs in the target vm, it guarantees that the operand stack is empty.

But, if I would like to saving all current thread stack state information抯 (Thread stack?local variables, pc厰, heap, method area), 揻rame by frame for thread stack? then I will restore them later. Is it guaranteed to no loss information抯 for frames other then the first?擝ecause the operand stack of the other frames not empty?

If no, Method entry event it must be applied at all frames when the application running, and save the proper information for each frame separately?

regards.

asmainfa at 2007-7-9 5:49:01 >