Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Debugger crashes when breakpoint exists #309

Closed
1 task done
paulkre opened this issue Nov 17, 2023 · 2 comments
Closed
1 task done

[BUG] Debugger crashes when breakpoint exists #309

paulkre opened this issue Nov 17, 2023 · 2 comments

Comments

@paulkre
Copy link

paulkre commented Nov 17, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Running :lua require 'dap'.continue() with Launch Flutter will result in a crash with the following error:

Error retrieving stack traces: type 'double' is not subtype of type 'int' in type cast

(It works in VSCode)

Expected Behavior

The debugger runs correctly and stops at the breakpoint.

Steps To Reproduce

  1. Create a new project with flutter create my_app
  2. Toggle a breakpoint in the main function
  3. Run :lua require 'dap'.continue() and select Launch Flutter

Environment

- OS: macOS 14.0
- Flutter version: 3.16.0
- Is flutter in $PATH: yes
- neovim version: 0.9.2

Anything else?

No response

@sidlatau
Copy link
Collaborator

I am facing the same issue. After some investigation, I found that this is a problem with the latest Flutter version 3.16.0. Looks like at some point thread IDs became int64, while in DAP it is expected to be int32 and that breaks the debugging. I see it is already reverted with this commit dart-lang/sdk@eda6963,
dart-lang/sdk#53086
But unfortunately looks like this commit was not released with the stable Flutter version. My current workaround is to use Flutter beta channel (Flutter 3.17.0-0.0.pre • channel beta), debugging works there.
So closing this issue, because there is nothing we can do in this plugin to fix it.

@bas-ie
Copy link

bas-ie commented Nov 21, 2023

Ah, I was finally getting used to being back on the stable channel! Oh well. Thanks for this, now I know I'm not going crazy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants