Debugger - broken step over and crashed when using labda #257

dkimitsa · 2018-01-22T14:24:05Z

It was not possible to step over code if this code was generating exception (even if it was handling it)
Debugger was incorrectly resolving scope of local variables if their usage was starting with invoking of lambda

…e there is an exception thrown (even handled one) in code that being stepped over/out. E.g. it was not possible to go through following code: new File("/some/invalid/path").exists(); new File("/some/invalid/path").exists(); as it throws/handles internal exceptions

…its first unit was set to lambda invocation code generated by RoboVM compiler. as during replacement of DynamicInvokeExpr it wasn't copied line number information

dkimitsa added 2 commits January 22, 2018 15:50

debugger: fixed bug: local variable scope resolution was broken when …

ea48c14

…its first unit was set to lambda invocation code generated by RoboVM compiler. as during replacement of DynamicInvokeExpr it wasn't copied line number information

florianf merged commit 81c9462 into MobiVM:master Jan 22, 2018

dkimitsa deleted the fix_debugger_steps_and_lambda branch January 23, 2018 10:05

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Debugger - broken step over and crashed when using labda #257

Debugger - broken step over and crashed when using labda #257

Uh oh!

dkimitsa commented Jan 22, 2018

Uh oh!

Uh oh!

Debugger - broken step over and crashed when using labda #257

Debugger - broken step over and crashed when using labda #257

Uh oh!

Conversation

dkimitsa commented Jan 22, 2018

Uh oh!

Uh oh!