The debugger and the debuggee are running in different versions of JVMs. You could see wrong source mapping results.
See original GitHub issueWhen trying to run a project (sometimes not even debugging) I keep getting this warning on vscode:
[Warn] The debugger and the debuggee are running in different versions of JVMs. You could see wrong source mapping results.
Debugger JVM version: 14.0.2
Debuggee JVM version: 11.0.13
The solution seems simple, all I want to is use the Debugger JVM as the 11.0.13. But I can’t find where I change this setting. Help please.
Issue Analytics
- State:
- Created 2 years ago
- Comments:14
Top Results From Across the Web
Cannot set JVM for debugger · Issue #907
1. Current Result. [Warn] The debugger and the debuggee are running in different versions of JVMs. You could see wrong source mapping results....
Read more >scalameta/metals - Gitter
[Warn] The debugger and the debuggee are running in different versions of JVMs. You could see wrong source mapping results. Debugger JVM version:...
Read more >visual studio code - VSCode Java Debugger Version change
[Warn] The debugger and the debuggee are running in different versions of JVMs. You could see wrong source mapping results.
Read more >Run and Debug Java in Visual Studio Code
See how you can run and debug your Java source code locally, and in the cloud. ... Another way to start debugging is...
Read more >Consolidated JDK 8 Release Notes
It is ideal if you want or need to use Java SE 8 and you are running those ... and key update behaviors...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Did you run
Metals: Restart build serverafterwards?It’s not require, but the only difference is that you don’t have the Bloop cli, everything else is the same, so the server should pick up bloop.json in home.
.blooponly contains config files for modules, so if you add another json it will think you added a new target, so this is not a right place to add anything manually.That’s separate setting, Metals doesn’t use Java Language Server currently.
Could you try to update to newest Metals snapshot? https://scalameta.org/metals/docs/ and changes server version settings.
The snapshot version should print the issues with connection to Bloop in detail.