Repository navigation
Debugger stopped working after upgrading to 0.3.1? #170
Description
Here is my configuration:
{ // Use IntelliSense to learn about possible attributes. // Hover to view descriptions of existing attributes. // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387 "version": "0.2.0", "configurations": [ { "type": "java", "name": "Debug (Launch)", "request": "launch", "mainClass": "com.xxxx.xxxxxx", "vmArgs": "-Xms2000m -Xmx3000m -Dspring.profiles.active=dev -Dspring.config.location=file:/Users/xxxxxx/app/src/main/resources/config/local/application.yml -agentpath:/Users/xxxxx/jrebel/lib/libjrebel64.dylib", "cwd": "${workspaceFolder}" } ] }
Not sure what happened, but it seems after upgrading to 0.3.1, the debugger stopped working. Once started, it shows "Compiling workspace" and then the following error.
I don't remember seeing "Compiling workspace" before, and I don't need it actually. Downgrading to 0.2.0 works.
Environment
- Operating System: Mac
- JDK version: 1.8.0_144
- Visual Studio Code version: 1.18.1
- Java extension version: 0.14.0
- Java Debugger extension version: 0.3.1
Activity
[-]Debugger stopped working after upgrading to VS Code 1.18.1?[/-][+]Debugger stopped working after upgrading to 0.3.1?[/+]gorkem commentedon Nov 20, 2017
I see the exact same behavior in my case it is trying to attach to an already running application.
ansyral commentedon Nov 20, 2017
Compiling the workspace should be removed for attaching case.
One known cause is that language server would link current src files into default project, which I'll investigate later. For this case, cleaning your local vscode storage folder(%AppData%\Code\User\workspaceStorage) would unblock it.
shawnwithlegion commentedon Nov 20, 2017
Xuan Zhou (@ansyral) Cleaning /workspaceStorage doesn't work for me.
snjeza commentedon Nov 20, 2017
Shawn Lan (@shawnwithlegion) try to remove the Java Debug extension, reload VS Code and reinstall it.
YousefSaber commentedon Nov 21, 2017
Snjeza (@snjeza)
I've tried this didn't work doesn't anyone knows how to fix this issue
snjeza commentedon Nov 21, 2017
Shawn Lan (@shawnwithlegion) try to remove the LS for Java by Red Hat extension and reinstall it.
shawnwithlegion commentedon Nov 21, 2017
Snjeza (@snjeza) I did but it didn't fix the issue. I had to downgrade to 0.2.0 for now.
wokhan commentedon Nov 22, 2017
Workaround: I had to manually modify the configurationProvider.js file to remove the compilation (in extensions\vscjava.vscode-java-debug-0.3.1\out\src).
Line 92: comment the whole try / catch so that compilation is not required anymore.
This should be an option (force recompilation everytime or not), as this is not exactly useful (code is recompiled automatically anyway on save...).
Nice extension anyway :-)
hnefatl commentedon Nov 22, 2017
Jérôme Saliba (@wokhan) Can confirm this works for me, with version 0.3.1.
shawnwithlegion commentedon Nov 22, 2017
Agreed with Jérôme Saliba (@wokhan). Forcing compilation every time should be an option.
akaroml commentedon Nov 27, 2017
Xuan Zhou (@ansyral) Jinbo Wang (@testforstephen) is this already resolved?
shawnwithlegion commentedon Nov 30, 2017
issue not fixed with 0.4.0. Not it's showing something like "the response is not either an error or...."
andxu commentedon Dec 1, 2017
Shawn Lan (@shawnwithlegion) are you using the latest version 0.15.0 of https://marketplace.visualstudio.com/items?itemName=redhat.java with the change log which contains full and incremental compilation.
shawnwithlegion commentedon Dec 4, 2017
Andy Xu(devdiv) (@andxu) works with 0.15.0. Thanks!
yaohaizh commentedon Dec 5, 2017
Close this as it has been fixed in the latest vscode-java/vscode-java-debugger.