Add the ability to disable the debugger

[oliveryasuna]

In some cases, it's useful to use a 3rd party debugger. Since the JVM does not allow multiple TI agents, we cannot simply add -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5005 to vmArgs.

Maybe a solution is to add an argument that, when true, does not add append -agentlib:jdwp=transport=dt_socket,server=n,suspend=y,address=localhost:62188 to the command.

[github-actions]

Hi @oliveryasuna, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

Suggested Workaround

• Instead of using the built-in Run/Debug CodeLens (which always injects -agentlib:jdwp=…), switch to an Attach launch configuration. That way you can start your JVM with your own debug agent (or no agent) and then connect:

  // .vscode/launch.json
  {
    "version": "0.2.0",
    "configurations": [
      {
        "type": "java",
        "name": "Attach to Remote",
        "request": "attach",
        "hostName": "localhost",
        "port": 5005
      }
    ]
  }

  • VS Code Java debug docs – Launch configurations: https://code.visualstudio.com/docs/java/java-debugging#_launch-configurations

Duplicate Issue

This request overlaps with an existing discussion on disabling or customizing the Run/Debug options in the Java Debug extension:

• Disabling or editing the Run Java/Debug Java options #1264 – “Disabling or editing the Run Java/Debug Java options”
  Disabling or editing the Run Java/Debug Java options #1264 (comment)

Other references with low confidence

(none)

The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!