|[cdt-dev] DSF debug view - thread suspended reason
Currently in DSF you can specify the reason why a thread was suspended, e.g. breakpoint, watchpoint, exception, etc, but it's an enum, and the reason text is hard coded. There's no way to specify more information about the reason, like what type of exception occurred, or what variable or memory address access caused a watchpoint to trigger. I can override ExecutionConextContentProvider to have it do what I want in our debugger, but it seems more natural to extend the DSF interfaces to support this generically since this is a typical debugger use case. Should I log a bug and attach a patch for this, or just override it in our debugger?
Back to the top