3

I'm running VSCode (v1.26.1) with the Java Extension Pack (v0.3.0) for remote debugging. When execution hits a breakpoint, VSCode does not open the file, though it correctly displays the filename in the call stack:

enter image description here

Instead, it displays the error:

enter image description here

I have the following in my launch.json:

enter image description here

Adding the sourcePaths property got VSCode to display the filename in the call stack for the line of code with the breakpoint. It previously displayed Unknown Source. But it still can't open the file. It appears that sourcePaths has only enabled VSCode to "sort of" find the source file.

Does anyone know what I need to do to get it to open the file when it hits the breakpoint (or when I click on the file in the call stack)?

Note: This question is different than this question in that I'm using Java Extension Pack's Debugger for Java and not the deprecated javaVSCode that was being used by the asker of that question.

Improve this question
Related questions
0
Eclipse debugger is blank (source not found)
1
Visual Studio Java debugger only supports starting the execution in a named class
0
Debugging java in VS 2015
Load 7 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.