Debugging in Codewind
Complete the following steps to debug in Codewind applications:
- In the Codewind view, right-click a project and select Restart in Debug Mode from the menu.
- Wait for the project state to switch to Debugging. After it switches to Debugging mode, the debugger is attached.
- When in Debugging mode and when the debugger is attached, you can debug your application. Perform debug actions that are supported by the IDE that you are using.
- While the project is still in Debugging mode, if the debug process is detached, right-click your project and select Attach Debugger from the menu. This action reattaches the debugger to the debug process, and you can continue with debugging your application.
- To switch back to run mode, right-click your project and select Restart in Run Mode from the menu.
Remote debugging is the same as local debugging with the following exceptions:
ocand make sure you are logged in to your cluster.
- After the project restarts in debug mode, Codewind automatically sets up a port forward from the application’s debug port to a port on your local machine.
Starting a debug session
- In Eclipse, for Node.js projects, a launch is created for the port forward that appears in the Debug view. For Java projects, the port forward is added as a process to the debug launch.
- In VS Code, the port forward is run as a VS Code task, which appears in the Terminal view. Ending a debug session
- In Eclipse, for Node.js applications where you use a Chromium-based browser for debugging, manually end the associated port forwarding process in the Debug view if you end the debug session in your browser.
- In Eclipse, for Java projects, if you detach the debugger or restart the application in run mode, both the debug session and the port forward are terminated automatically.
- In VS Code, if you close the debug session, the port forward task stays active in the Terminal view.
- In Eclipse and VS Code, if you close the port forward, the debug session terminates because the debug port is no longer accessible from the local machine.
Using Java hot code replace while debugging
If you want to use Java hot code replace and change your code while you debug, disable automatic builds.
- To disable automatic builds, right-click your project in the Codewind Explorer view and select Disable Auto Build.
- If you want to start a build while automatic builds are disabled, right-click your project and select Build.
- Enable automatic builds again after you finish debugging. To enable automatic builds again, right-click your project and select Enable Auto Build.
Debugging initialization code for Java projects
- If you want to debug initialization code, set breakpoints in the code. You can also set breakpoints in your application code.
- When you debug initialization code, wait for the project state to change to Debugging or for the debugger to stop at a breakpoint.
- Normally you can reload your application multiple times to isolate a problem. However, when you debug initialization code, restart your project in debug mode to stop in the code again.
Debugging Node.js projects in Eclipse
In Eclipse, to restart your Node.js application in debug mode, the tools help you launch a debug session in a Chromium-based web browser.
- Right-click the project in the Codewind Explorer view and select Restart in Debug Mode.
- Follow these steps if you’re prompted to select a Chromium-based web browser for launching the debug session:
- Select a Chromium-based browser from the list of browsers or use the Manage link to add one.
- Optionally, select to always use this browser for Node.js debugging.
- Click OK to continue.
- Launch a debug session using the information on the Node.js Debug Inspector URL dialog:
- To copy the debug URL, click Copy URL to Clipboard.
- To open the browser you selected in the previous dialog, click Open Browser.
- Paste the URL into the address bar of the browser to start the debug session.