You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Java debugger will use the API System.getProperty("java.home") to resolve java bin path, and use it to launch the debuggee. For windows, the value of System.getProperty("java.home") is read from the registry HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft, and it's generally pointing to the JRE. This is the reason why the debuggee is launched in JRE instead of JDK.
To fix the issue, we need read the java bin path from the user environment variable JAVA_HOME. And follow Java Language Server to use the same JDK to launch the debuggee.
Launching the debuggee with the correct JDK still has similar local variable name missing issue when debugging JDK source code. The JDK library is located in rt.jar, but the rt.jar in the official oracle JDK installation doesn't contain the debug symbol for the local variables. That's why the debugger cannot get the correct parameter names and local variable info for JDK method.
Steps:
Open any project and write "new String("");" and step in the String constructor,
The variable should be two:
but actual the parameter for String constructor is arg0 which indicating that the program is running at jre env,eg:
The text was updated successfully, but these errors were encountered: