Warn users when there are breakpoints on SDK/Packages that won't be hit due to debug settings

Seen result: I can place breakpoints inside of my unit test and execution will pause correctly, but if I put a breakpoint in the framework, say packages/flutter/lib/src/widgets/scroll_physics.dart the breakpoint will not trigger.

Expected result: I expect breakpoints in the framework to behave like breakpoints in the unit tests.

Seen system: Dart Code Version: 3.10.1 VSCode: 1.44.2 Operating System: Mac OS X 10.14.6

Flutter Doctor:

[✓] Flutter (Channel unknown, 1.18.0-9.0.pre.66, on Mac OS X 10.14.6 18G2022, locale en-US)
    • Flutter version 1.18.0-9.0.pre.66 at /Users/aaclarke/dev/flutter
    • Framework revision 780d93bf38 (19 hours ago), 2020-05-04 17:18:41 -0700
    • Engine revision 4bcfae82c7
    • Dart version 2.9.0 (build 2.9.0-3.0.dev a69cb6d700)

Notes:

• If I use the debugger() function in my desired code, execution will pause but the stack trace inside of visual studio code will not include anything beyond the unit test.

[DanTup]

Neither of my other ideas worked, so the best I could come up with for now is this when you have a breakpoint outside of your current workspace. If you already have them, this will appear at project open, but otherwise it’ll appear as soon as you add the breakpoint:

It will only prompt once per session (and if you click Never Ask it won’t ask again).

[gaaclarke]

With this off, ehen an exception occurs in the framework, it will break the debugger where your code called into the framework.

Makes sense, thanks @DanTup. Also, in lieu of a warning we could consider just treating explicit breakpoints as exceptions to the settings, too. That might be easier. I think it’s a pretty clear signal someone wants it to break there if they go through the trouble of adding the breakpoint.