Read in environment variable for C debug process from file
up vote
0
down vote
favorite
I'm debugging a C program which will listen on a localhost TCP port depending on an environment variable PORT_BIND
(which unfortunately cannot be UNIX domain socket). I want to debug several processes of the program in different workspaces (code checkouts of different branches in different paths) in parallel with VSC, so I want the port on which the program is listing to be dependent on the path of the workspace, e.g. on a configuration file port_for_workspace.txt
. I connect to the program with an external testsuite (source also in the repository), so it needs to read the port as well, but I have more leeway there, as I can write some wrapper around that to read the port number.
Ideas I had that lead nowhere:
- use
envFile
attribute of launch configuration => the attribute exists for Python or Nodejs launch configurations and but not for C/C++ launch configurations apparently. - use the environment attribute of a C/C++ launch configuration in combination with the variable substitution
${command:CommandID}
which can paste in the result of a VSC command => I could not find a command to paste the contents of a file - use gdb setupCommands in the launch configuration to load set environment variable from gdb => I couldn't find a way to load a file in a convenience variable or to set an environment variable to the contents of a convenience variable
Any thoughts?
visual-studio-code
add a comment |
up vote
0
down vote
favorite
I'm debugging a C program which will listen on a localhost TCP port depending on an environment variable PORT_BIND
(which unfortunately cannot be UNIX domain socket). I want to debug several processes of the program in different workspaces (code checkouts of different branches in different paths) in parallel with VSC, so I want the port on which the program is listing to be dependent on the path of the workspace, e.g. on a configuration file port_for_workspace.txt
. I connect to the program with an external testsuite (source also in the repository), so it needs to read the port as well, but I have more leeway there, as I can write some wrapper around that to read the port number.
Ideas I had that lead nowhere:
- use
envFile
attribute of launch configuration => the attribute exists for Python or Nodejs launch configurations and but not for C/C++ launch configurations apparently. - use the environment attribute of a C/C++ launch configuration in combination with the variable substitution
${command:CommandID}
which can paste in the result of a VSC command => I could not find a command to paste the contents of a file - use gdb setupCommands in the launch configuration to load set environment variable from gdb => I couldn't find a way to load a file in a convenience variable or to set an environment variable to the contents of a convenience variable
Any thoughts?
visual-studio-code
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm debugging a C program which will listen on a localhost TCP port depending on an environment variable PORT_BIND
(which unfortunately cannot be UNIX domain socket). I want to debug several processes of the program in different workspaces (code checkouts of different branches in different paths) in parallel with VSC, so I want the port on which the program is listing to be dependent on the path of the workspace, e.g. on a configuration file port_for_workspace.txt
. I connect to the program with an external testsuite (source also in the repository), so it needs to read the port as well, but I have more leeway there, as I can write some wrapper around that to read the port number.
Ideas I had that lead nowhere:
- use
envFile
attribute of launch configuration => the attribute exists for Python or Nodejs launch configurations and but not for C/C++ launch configurations apparently. - use the environment attribute of a C/C++ launch configuration in combination with the variable substitution
${command:CommandID}
which can paste in the result of a VSC command => I could not find a command to paste the contents of a file - use gdb setupCommands in the launch configuration to load set environment variable from gdb => I couldn't find a way to load a file in a convenience variable or to set an environment variable to the contents of a convenience variable
Any thoughts?
visual-studio-code
I'm debugging a C program which will listen on a localhost TCP port depending on an environment variable PORT_BIND
(which unfortunately cannot be UNIX domain socket). I want to debug several processes of the program in different workspaces (code checkouts of different branches in different paths) in parallel with VSC, so I want the port on which the program is listing to be dependent on the path of the workspace, e.g. on a configuration file port_for_workspace.txt
. I connect to the program with an external testsuite (source also in the repository), so it needs to read the port as well, but I have more leeway there, as I can write some wrapper around that to read the port number.
Ideas I had that lead nowhere:
- use
envFile
attribute of launch configuration => the attribute exists for Python or Nodejs launch configurations and but not for C/C++ launch configurations apparently. - use the environment attribute of a C/C++ launch configuration in combination with the variable substitution
${command:CommandID}
which can paste in the result of a VSC command => I could not find a command to paste the contents of a file - use gdb setupCommands in the launch configuration to load set environment variable from gdb => I couldn't find a way to load a file in a convenience variable or to set an environment variable to the contents of a convenience variable
Any thoughts?
visual-studio-code
visual-studio-code
asked Nov 22 at 14:08
Perseids
7,03632348
7,03632348
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53432771%2fread-in-environment-variable-for-c-debug-process-from-file%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown