Repository navigation
vmArgs in launch.json does not accept an array of strings #778
Copy link
Copy link
Closed
Description
Activity
testforstephen commented
on Mar 17, 2020 ContributorMore actionsplease share your launch.json and the version of Debugger for Java extension.
{ // Use IntelliSense to learn about possible attributes. // Hover to view descriptions of existing attributes. // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387 "version": "0.2.0", "configurations": [ { "type": "java", "name": "BitwigStudio - Debug", "request": "launch", "mainClass": "com.bitwig.flt.app.BitwigStudioMain", "projectName": "float-main-app", "cwd": "${workspaceFolder}/float/app/gui/main-app", "vmArgs": [ "-ea", "-Xmx1024m", "-Xms256m", "-Xss24m", "-XX:MaxPermSize=256m", "-XX:-UseLoopPredicate", ], "linux": { "vmArgs": [ "-XX:ErrorFile=${HOME}/.BitwigStudio/bitwig-studio-jvm-crash.log", "-DvampExecutable=${workspaceFolder}/cmake-builds/debug-64/bin/BitwigVampHost", "-DvampPath=${workspaceFolder}/cmake-builds/debug-64/vamp-plugins", "-DengineExecutable=${workspaceFolder}/cmake-builds/debug-64/bin/BitwigAudioEngine", "-DpluginHostExecutable32=${workspaceFolder}/cmake-builds/debug-32/bin/BitwigPluginHost", "-DpluginHostExecutable64=${workspaceFolder}/cmake-builds/debug-64/bin/BitwigPluginHost", "-DwindowingSystems=com.bitwig.x11_windowing_system.X11WindowingSystem", "-Dshow-file-dialog-command=${workspaceFolder}/float/installer/src/main/distribution-linux/bin/show-file-dialog-gtk3" ] }, }, { "type": "lldb", "request": "launch", "name": "AudioEngine", "program": "cmake-builds/code/bin/BitwigAudioEngine", "cwd": "${workspaceRoot}" } ] }I have Debugger for Java version 0.25.1
testforstephen commented
on Mar 18, 2020 ContributorMore actionsthanks for the info. i can reproduce the issue. The reason is the debugger doesn't well handle the OS specific attribute (e.g.
"linux": { "vmArgs": [] }) in launch.json. Currently, the workaround is to remove the linux specific vmArgs first.
When configuring a java debugger target, in launch.json, it seems that vmArgs does not accept an array of strings. Note that I've configured vmArgs in the linux section as well.
Environment
Backtrace: