[WSL] Breakpoints fail to bind when attaching to JVM in WSL2 after Debugger for Java 0.58.3 update; rollback fixes

[clertonbruno]

Environment:

• Host OS: Windows 11, IDE: Cursor/VS Code
• Guest: WSL2 Ubuntu 22.04
• Java: OpenJDK 1.8.0_432 (Java 8)
• Extensions: Debugger for Java 0.58.3 (latest), Language Support for Java 1.47.0
• Spring Boot app running inside WSL2, debugged via JDWP attach on port 5005.

Expected:
Attaching from Windows (Cursor/VS Code) to a JDWP-enabled JVM in WSL2 stops at breakpoints in my project code.

Actual:
After updating to Debugger for Java 0.58.3 and Language Support for Java 1.47.0, attach no longer stops at breakpoints. HTTP requests hang as if the breakpoint is hit, but the IDE never jumps to the code. Attaching using jdb and setting the same breakpoints works fine, so JDWP and class debug info are good.

Rolling both extensions back (Debugger for Java 0.58.2 and Language Support for Java 1.46.0) restores proper behaviour.

Repro steps:

1. Build and run the Spring Boot jar in WSL2 with JDWP:

java -agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=5005 \
  -Dspring.profiles.active=local -Duser.timezone=UTC \
  -jar build/libs/your-app.jar

2. In Windows Cursor/VS Code, attach to 127.0.0.1:5005 (port forwarded via Remote - WSL).
3. Set a breakpoint in any controller method.
4. Send an HTTP request hitting that controller.
5. Observe: request hangs but IDE never shows breakpoint. Meanwhile, jdb attach shows that the breakpoint is hit.

Notes:

• This only occurs when the JVM runs in WSL2 and the IDE is on Windows. A colleague running everything natively on Windows (no WSL) doesn't see the problem.
• address=*:5005 can't be used with Java 8 due to gethostbyname errors.
• This seems like a regression introduced in 0.58.3 (or 0.58.3 + language server update). Rolling back fixes the issue.

Thanks for looking into this.

[github-actions]

Hi @clertonbruno, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

Suggestions:

• Use source mapping so the debugger can bind breakpoints to files under WSL2. In your launch.json attach configuration add something like:

{
  "type": "java",
  "request": "attach",
  "hostName": "127.0.0.1",
  "port": 5005,
  "sourcePaths": [
    {
      "remoteRoot": "/home/your-user/your-project",
      "localRoot": "${workspaceFolder}"
    }
  ],
  "trace": "verbose"
}

– See Remote debug docs: https://code.visualstudio.com/docs/java/java-debugging#_configure-the-remote-debug-settings

• Enable verbose logging to capture why breakpoints don’t bind:
– Add "trace": "verbose" and inspect the DEBUG CONSOLE for messages about class loading and breakpoint mapping.

• As a temporary workaround, rollback to Debugger for Java 0.58.2 & Language Support for Java 1.46.0.

• If this persists, please file an issue including the verbose logs.

High-confidence references:

• Breakpoints not working after recent update (similar symptom of ignored breakpoints) — microsoft/vscode-java-debug#1364

Other references with low confidence

• Breakpoints not working at all in 0.58.x series — microsoft/vscode-java-debug#1531
• Spring/WSL2 debug lands in platform classes, not user code — microsoft/vscode-java-debug#795

The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!