VS reports "Unable to step. The message was improperly formatted..." on signal during eval

In the following log segment an eval terminates with a signal. This is not reported to the users and he is left in a state with a bad stack, and no indication of what happened.

2: (44083) <-1126-var-create - * "strlen(sqlite3_column_text(statement, 3))"
2: (44122) ->"\nProgram received signal "
2: (44122) ->"SIGSEGV, Segmentation fault.\n"
2: (44131) ->1126^done,reason="signal-received",signal-name="SIGSEGV",signal-meaning="Segmentation fault",frame={addr="0x00007ffff745fdbb",func="??",args=[]},name="var8",numchild="0",value="",type="int",thread-id="2",has_more="0"
2: (44131) ->(gdb)
2: (44131) 1126: elapsed time 48
2: (44133) <-1127-var-evaluate-expression var8
2: (44141) ->1127^done,value=""
2: (44141) ->(gdb)
2: (44141) 1127: elapsed time 8
2: (44168) <-1128-var-create - * "init_gw_list_from_dtb()"
2: (44171) ->1128^error,msg="-var-create: unable to create variable object"
2: (44171) ->(gdb)
2: (44171) 1128: elapsed time 3
2: (44202) <-1129-var-create - * "g"
2: (44212) ->1129^error,msg="-var-create: unable to create variable object"
2: (44212) ->(gdb)
2: (44212) 1129: elapsed time 10
2: (45047) <-1130-exec-next
2: (45055) ->1130^error,msg="Cannot find bounds of current function"

No source file or test is named. Start by tracing MIEngine handling for the logged -var-create response after signal-received, then follow the subsequent -var-evaluate-expression and -exec-next commands. Done should include reporting the signal to the user without leaving the debugger in a bad-stack state.