|Language||Required Plugin||Dev Image Required|
|Java||Debugger for Java||N/A|
The path to the Java Development Kit can be specified by the
java.home setting in VS Code settings (workspace/user settings). If not specified, it is searched in the following order until a JDK meets current minimum requirement,for extension jdk configuration, see Setting the JDK.
- on the current system path
The extension uses a few command-line tools developed by the Go community。in particular,
dlv must be installed for this extension to work correctly. See the tools documentation for a complete list of tools the extension depends on.
In order to locate these command-line tools, the extension searches
GOPATH/bin and directories specified in the
PATH environment variable (or Path on Windows) with which the VS Code process has started. If the tools are not found, the extension will prompt you to install the missing tools and show the "⚠️ Analysis Tools Missing" warning in the bottom right corner. Please install them by responding to the warning notification, or by manually running the
Go: Install/Update Tools command.
- Select the workload that you want to debug
- Right-click the workload and select
Dev Config, configure your debugging configuration
- Then right-click this workload again and select
- Nocalhost will automatically install the dependencies on the first debug
- Nocalhost will automatically enter the
DevModeand start remote debugging
The development environment is different between developers. You should configure remote debug configurations according to the actual situation.
The shell command for Maven example:
For jdk <=1.7 you should replace
For lower version of the springBoot you should replace
The startup command for Gradle example:
How does it Works?
Nocalhost using pydevd to debug Python application.
How does it works?
Nocalhost using Xdebug to debug PHP applications.
nocalhost will automatically configure
vscode when debug is finished, next time you can launch debug directly with shortcut key
debug supports custom parameters to start, you just need to add parameters under
launch.json, and the plugin will pass the parameters to the debugger when debug is launched.
If you need to enable diagnostic output when debugging a
Node.js application, you just need to change the following configuration.
The java debugger stops at
return ma.invoke(obj, args);in the
Java: Clean the Java language server workspace command