-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Macos: cppdbg ignores launch.json cwd #8052
Comments
Can you enable logging and share the output from the
In the debug adapter, we send
You can also run |
Hi Andrew, many thanks for your quick response, really appreciate your assistance... Here is the output when I enable logging and trace:
|
When I run
|
GDB's working directory is
but for some reason the inferior process is This may be a bug in lldb where it does not properly update the working directory after updating the debugger's working directory.
This means lldb-mi did not implement this gdb MI interface and may not have the correct commands to set the working directly correctly. |
This issue has been closed automatically because it's labeled as 'external'. |
Thank you Andrew! very much appreciate your help. I'll follow up with llbd-mi! Kind regards, |
Bug type: Debugger
Describe the bug
When debugging the application on macos using vscode's C/C++ for Visual Studio Code extension, I would expect the executable to be launched from the ${workspace} folder, as I have specified cwd in launch.json. However, the executable is launched from the build folder, where the executable is located.
To Reproduce
please see newdigate/vscode-cpptools-macos-cppdbg-cwd-issue. This should help you to easily reproduce the issue.
Steps to reproduce the behavior:
launch.json
in .vscode:build
folder where the executable will resideThe text was updated successfully, but these errors were encountered: