-
Notifications
You must be signed in to change notification settings - Fork 6
Open
Description
Hello,
I am trying to configure debugging for a C++ project in VS Code using your extension. My launch.json so far based on cppdbg uses the pipeTransport option to launch the debugger through a custom script. I would like to confirm whether pipeTransport is officially supported in this context, and if there are any known limitations or requirements for its use.
Here is a snippet from my configuration:
"type": "cppdbg",
"request": "launch", // Launch -> we start the process
"name": "Directly debug component tests",
"program": "test_CT",
"args": [
"'${input:testName}'",
"'./report.xml'",
"'0'"
],
"cwd": "${workspaceRoot}/Build/.gdb/root/",
"externalConsole": true,
"pipeTransport": {
"pipeCwd": "${workspaceRoot}",
"pipeProgram": "bash",
"pipeArgs": [
"magic_script.sh",
"debug",
"--targets=Program",
"--test-name=${input:testName}",
"--command"
],
"debuggerPath": "/usr/bin/gdb"
}
Could you please clarify if this setup is supported and if there are any best practices or documentation available for using pipeTransport?
Thank you!
Metadata
Metadata
Assignees
Labels
No labels