-
Notifications
You must be signed in to change notification settings - Fork 94
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
Debugger doesn't seem to start with 2.0.10, but works with 2.0.9 #298
Comments
I confirm, that happens on my setup as well (VSCode 1.92.0, Ubuntu 24.04, Lua 5.4). |
and i can confirm same (debian bookworm, vscode 1.91.1, lua53) |
and i can confirm same (arch, vscode 1.92.2, luajit) |
Can confirm with VSCode:
I'm using a Docker devcontainer if that makes any difference. Also had the same issue with VSCode 1.85.1 Downgrading to 2.0.9 solves the issue |
This snippet from the comparison between 2.0.9 and 2.0.10 looks strange to me. Commit is here 2a353aa but doesn't give much information which bug and why? Original code filtered events to EPOLLIN or EPOLLOUT when event EPOLLERR or EPOLLHUP comes. New code just adds those events (both; even if they're not there) -- no idea why, but this could be legit: https://stackoverflow.com/a/29206631/1116364 |
2.0.9 does not work for me either. |
@actboy168 Is this commit a6a380e referring to this bug here? |
The debugger doesn't seem to start with 2.0.10, but it works with 2.0.9.
For 2.0.10, nothing happens when starting a debug session. VS Code just shows that "something is loading" for about a second, and then nothing more. I didn't manage to find any logs.
I'm using WSL with Devcontainer and Lua 5.4. Attached zip with setup: proj.zip
The text was updated successfully, but these errors were encountered: