You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I have "[Stop on] Uncaught exceptions" checked in VS Code, sometimes the debugger will stop when an exception is obviously caught, if there is an async gap between the try-catch and where the exception is thrown:
Example: await client.openStreamingConnection is clearly within a try-catch block, yet the runtime reports that the exception is unhandled, and the debugger stops on the exception as uncaught.
If providing this information as part of reporting a bug, please review the information
below to ensure it only contains things you're comfortable posting publicly.
General info
Dart 3.5.0-131.0.dev (dev) (Fri May 3 09:02:58 2024 -0700) on "linux_x64"
We would need a reproduction of the behavior you are seeing or at least more code pasted as text with clear description of what is happening. (e.g. here is the code in each frame on the stack, here is where exception is thrown, here is where debugger has stopped, etc).
mraleph
added
area-vm
Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends.
needs-info
We need additional information from the issue author (auto-closed after 14 days if no response)
labels
May 11, 2024
FWIW I can also see that exception is reported to the console as unhandled. So if that's the same exception the debugger stops for then debugger is correct.
github-actionsbot
removed
the
needs-info
We need additional information from the issue author (auto-closed after 14 days if no response)
label
May 12, 2024
I spent considerable time trying to debug this, but couldn't follow the logic in this callback-based code. There are all sorts of weird (primitive Dart) conventions like capturing a stacktrace anywhere you think you may asynchronously throw an error in future, and then passing it into the async call...
If I have "[Stop on] Uncaught exceptions" checked in VS Code, sometimes the debugger will stop when an exception is obviously caught, if there is an async gap between the try-catch and where the exception is thrown:
Example:
await client.openStreamingConnection
is clearly within atry
-catch
block, yet the runtime reports that the exception is unhandled, and the debugger stops on the exception as uncaught.Workspace Environment
Output from 'dart info'
/opt/flutter/bin/cache/dart-sdk/bin/dart info
If providing this information as part of reporting a bug, please review the information
below to ensure it only contains things you're comfortable posting publicly.
General info
Project info
Process info
Output from 'flutter doctor'
/opt/flutter/bin/flutter doctor -v
The text was updated successfully, but these errors were encountered: