`set env` commands with newlines trigger GDB problems
bspeice opened this issue · 1 comments
bspeice commented
Related: matepek/vscode-catch2-test-adapter#364, microsoft/vscode-cmake-tools#2442
Environment variables that contain newline characters cause problems when attempting to run set env
commands (gdb.cs and Debugger.cs), I believe because newlines aren't escaped properly (Debugger.cs). Downstream VS Code plugins have so far worked around this by removing environment variables containing newlines.
I'm currently working to set up a local copy of OpenDebugAD7 to test whether variable escaping is enough to fix the problem, but wanted to raise the issue here in case one of the maintainers had a better solution in mind.
bspeice commented