Steps to reproduce: 1. Open 2nd-level inspector, debugging sidebar, and scroll down so "Pause Reason" section is hidden. 2. Turn on "break on uncaught exceptions" 3. eval "throw Error" to make 1st-level inspector pause At this point, the dashboard view says the debugger is paused at some line, but it's not clear why its paused. There are several ways that this could be fixed: * Auto-reveal "pause reason" section on pause (possibly excluding normal breakpoint hits) * List pause reason "type" (Exception, debugger statement, Breakpoint) in debugger dashboard * Show exception message inline like we do for errors.
<rdar://problem/20346975>
I'm in favor of auto-revealing the cal stack on pause.
I agree. This has annoyed me once recently.