Your proposal
I'd like to catch exceptions of an arbitrary class via DAP (Debug Adapter Protocol), just like the console UI's catch MyError command.
Currently it is not possible to catch exceptions by specifying an arbitrary class via DAP.
I believe this can be achieved by handling the exceptionOptions argument of the setExceptionBreakpoints request and enabling the corresponding capability.
Reference: setExceptionBreakpoints in the DAP specification
https://microsoft.github.io/debug-adapter-protocol//specification.html
supportsExceptionOptions is listed as "Will be supported" in
Additional context
Background:
While developing an MCP server for the debug gem, I ran into the problem that catching an exception of a specific class is not possible via DAP.
rira100000000/debug-mcp
The standard filters are only two: any (all exceptions) and RuntimeError, so currently the only choices are catching every error or catching only RuntimeError.
With any, every Exception is caught — including ones raised internally by frameworks such as Rails — which produces a lot of noise before you reach the exception you actually care about.
Your proposal
I'd like to catch exceptions of an arbitrary class via DAP (Debug Adapter Protocol), just like the console UI's
catch MyErrorcommand.Currently it is not possible to catch exceptions by specifying an arbitrary class via DAP.
I believe this can be achieved by handling the
exceptionOptionsargument of thesetExceptionBreakpointsrequest and enabling the corresponding capability.Reference:
setExceptionBreakpointsin the DAP specificationhttps://microsoft.github.io/debug-adapter-protocol//specification.html
supportsExceptionOptionsis listed as "Will be supported" indebug/lib/debug/server_dap.rb
Line 169 in 6510cfb
Additional context
Background:
While developing an MCP server for the debug gem, I ran into the problem that catching an exception of a specific class is not possible via DAP.
rira100000000/debug-mcp
The standard filters are only two:
any(all exceptions) andRuntimeError, so currently the only choices are catching every error or catching onlyRuntimeError.With
any, everyExceptionis caught — including ones raised internally by frameworks such as Rails — which produces a lot of noise before you reach the exception you actually care about.