I could reproduce doing:

run until I got a call on Void
put a breakpoint on {ISE_EXCEPTION_MANAGER}.constructed_exception_chain  (last bp index)

and try to evaluate expression

l_exception.stack_trace

It seems to be due to missing context.init_variable_scopes  when checking expression for exp evaluator. (This seems to be done on the process_routine... level, so this seems logicial, we need to add such initialization somewhere, probably on {AST_DEBUGGER_EXPRESSION_CHECKER_GENERATOR}.expression_or_instruction_type_check_and_code

I will test this solution .. soon.