Do not break on exceptions thrown in undebuggable code if caught in undebuggable code #53755
Labels
area-vm
Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.
P3
A lower priority bug or feature request
triaged
Issue has been triaged by sub team
vm-debugger
See flutter/devtools#5883 for discussion.
There are several issues where users were confused by the the "Break on all exceptions" option when an exception is thrown in core library code and handled in core library code, e.g.
#52615
#52423
If an exception is thrown in code that is not debuggable and will be caught in code that is not debuggable, then the debugger should not break even if "Break on all exceptions" is enabled.
For example:
Calling
bar
should not cause the debugger to break onthrow Exception('foo');
because the exception is both thrown and caught in undebuggable code i.e. it is just an implementation detail ofbar
.Another example:
Calling
bar
should cause the debugger to break onthrow Exception('foo');
because the exception is caught in debuggable code.The text was updated successfully, but these errors were encountered: