Ignore failed stack-list-frames

Trying to debug bare metal on an embedded target. This means I'm not interested in pausing or breakpointing anything and that there doesn't really exist any stack to fetch.

But due to stack-list-frames being called anyway, and throwing an exception upon failing, gdb is quit and the debug session ends. See the log:

1: (561) <-1014-stack-list-frames 0 1000
=thread-selected,id="1"
1: (568) ->1014^error,msg="Cannot access memory at address 0xa404"
1: (568) ->(gdb)
1: (568) 1014: elapsed time 7
1: (569) Stack walk failed on thread: 1
ERROR: Unable to start debugging. Failed to find thread 1 for break event
1: (578) <--gdb-exit

How do I either omit stack-list-frames being called or simply ignore the exception being thrown? Or better yet, how do I disable or modify some of the default commands being fired?

E.g

gdb-set target-async on
gdb-set solib-search-path [path]
interpreter-exec console "info sharedlibrary"
stack-list-frames 0 1000

See https://github.com/Microsoft/vscode-cpptools/issues/321 for more background info.

No source files or tests are named. Start by tracing the logged stack-list-frames command and the default GDB/MI command sequence, then determine where its failure ends the session and whether command selection is configurable. Done means a failed stack-list-frames no longer terminates this debugging session, or the default command can be omitted or modified.