After several sub calls, on leaving a breakpointed function the debug window does not return to usual state (so can't get dialog to do more transactions)

[DaveAppleton]

Following the previous issue do the following

set a breakpoint at

And note debug state is

Now - setBanker to MYR / 0xdedb49385ad5b94a16f236a6890cf9e0b1e30392

ApproveUser : MYR / 0xdedb49385ad5b94a16f236a6890cf9e0b1e30392

then depositCash

(Love the showing of variables)

Then keep stepping in

481->482->481->483->(goes through function to return to 483)->481->86

At this time it is clear that the values of b are wrong ! 256000 represents exp = 3, val = 1 but I will visit that in another report

Trace it 86, 89, 92 fails to go to 90 despite debugger saying that b.exponent > a.exponent

step over 92 res.value has not been assigned

If you now resume, it gets out to the breakpoint again. Resume once more and you get

Which means that you can no longer get the contract interface back up. (right hand panel should be showing the contract space again as in second image.

[DaveAppleton]

Scratch the last bit - I am stupid - missed the sandbox tab - sorry.

[DaveAppleton]

Seems that despite the debugger issues above, the real calculations happened correctly

[3esmit]

I'm having the same issue. Seems like the transactions stop being mined. Quering a constant state function works, but transactions that need to be mined are hanged.

[3esmit]

This happens when using scenarios.

[romanman]

yep that is important stability issue

[asinyagin]

Fixed