CLI threads command does not include exception/call reason.
|Reported by:||anevilyak||Owned by:||anevilyak|
The debugger CLI's "threads" command currently lists a thread's state, but does not actually include the reason for the stopped state, i.e. the message passed to a deliberate debugger call. It needs to, especially for things like app_server crashes due to hitting an assert.