Ability to specify visualizerFile (and other launch configuration options) in debug config

[twhittock-disguise]

Checklist

• Checked Support page

Is your feature request related to a problem? Please describe.
When debugging my tests, it is frustrating that I am unable to use C++ natvis visualisation files. This is because they are added to my launch configurations in the visualizerFile section.

I am unable to use my launch configurations as it's unclear if/how the executable name and arguments are passed to the configuration.

Describe the solution you'd like
I'd like to either be able to use a generic launch configuration with this extension filling in the appropriate executable and command line arguments, or be able to specify all the launch configuration options in the debug.configTemplate section.

Describe alternatives you've considered
There is a workaround - copy the .natvis files from my project into ~/.vscode(-insiders)/extensions/ms-vscode.cpptools-x.y.z/debugAdapters/vsdbg/bin/Visualizers but this will frequently break due to the cpptools extension being updated.

Additional context
None

[matepek]

Hello,

Did you find this doc?

[twhittock-disguise]

Hi yes I read the documentation - I didn't see anything around specific launch config options though? Did I miss it?

[matepek]

At first read, I think the usable variables section answers your question. If not, please elaborate on your issue.

[twhittock-disguise]

Hi.

Sorry I don't understand how parameterising the debug config can make it use options from launch.json.

Here's an example launch.json config object

        {
            "name": "myprog",
            "type": "cppvsdbg",
            "request": "launch",
            "program": "${workspaceFolder}/build/${command:cpptools.activeConfigName}/myprog.exe",
            "visualizerFile": ".vscode/visualiser.natvis",
            "preLaunchTask": "build",
        },

Elements like preLaunchTask and visualizerFile aren't available in the debug config object, that I can see.

[matepek]

This extension does not do any debugging, it uses the debug adapters/extensions.

Don't depend on launch config. Try setting your testMate.cpp.debug.configTemplate. All the mentioned variables are available there.

[twhittock-disguise]

Yes, debugging works fine using the debug.configTemplate configuration. This issue was raied due to the lack of several things which are present when debugging using a launch command instead.

Specifically, the visualizerFile option is not applied when debugging tests. Also things like the preLaunchTask are helpful checks to ensure I am always debugging the latest code. There are a few of these, those are the ones I use, especially the visualizerFile, as some of my types are a pain to debug without it.

[matepek]

preLaunchTask not run I'm not sure it is the issue of this extension because this extension just passes whatever debug config it gets. That applies to other json properties.

check log message 'debug config data' and 'resolved debugConfig:'.

preLaunchTask probably can be circumvented with advancedExecutable before property.