-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error setting environement variables with a length > 1966 chars in the debugger through the environment file #8411
Comments
The error can be reproduced for values with a length > 1966 characters. I will update the description of the issue |
This would be an issue on lldb-mi. Their max buffer size seems to be 2048. See https://github.com/lldb-tools/lldb-mi/blob/87e390195fd2d2c40bb4154a51b0e7e003b6b9c8/src/MICmnStreamStdin.h#L58 |
Thanks, increasing the buffer command value x10 fixes the issue. I will open a new PR. |
Increase the command buffer size x10 to support passing long environment variables. This is required in projects like GStreamer requiring to setup env variables like GST_PLUGIN_PATH with several directories in order to be able to debug without having to install into a prefix, which takes a long time and slows down the development cycle. microsoft/vscode-cpptools#8411 microsoft/vscode-cpptools#6874
Increase the command buffer size x10 to support passing long environment variables. This is required in projects like GStreamer requiring to setup env variables like GST_PLUGIN_PATH with several directories in order to be able to debug without having to install into a prefix, which takes a long time and slows down the development cycle. microsoft/vscode-cpptools#8411 microsoft/vscode-cpptools#6874
Closing as external. |
Bug type: Debugger
Describe the bug
settings set target.env-vars
. Other shorter environment variables are set correctly. Setting the same longer environment variable in lldb succeeds as expected. The error can reproduced when the value of the env variable is > 1966 charactersTo Reproduce
launch.json
env file
Steps to reproduce the behavior:
Run -> Start debugging
The text was updated successfully, but these errors were encountered: