SOS tests fail when cdb has debug symbols for CoreCLR/CoreRun #59
Description
When running the debugger tests in a configuration where cdb loads symbols for CoreCLR and/or CoreRun, SOSRunner gets confused by templated functions in the output of !DumpStack. In particular, templated destructors and lambdas both can end in a >, which causes SOSRunner to incorrectly recognize these lines as containing a prompt. Two example functions that confuse SOSRunner under the current scheme: * CoreCLR!CAutoTryCleanup::~CAutoTryCleanup * CoreRun!__acrt_lock_and_call< > (apparently cdb adds an extra space between >s when demangling the lambda argument to the template) When I hardcode the prompt to be 0:000>, which it always seems to be on my machine, the tests pass, though I'm not sure that's the correct solution.
The fix will require a way to run commands and print something when the command is finished that isn't so ambiguous. Similar to what we do for LLDB.