microsoft / microsoft/vscode-cpptools
gdb debugger set auto-load safe-path / no effect
Open
Nobody has claimed this yet.
debugger
help wanted
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Type: Bug
- create any cmake project.
- use gdb debugger to debug app
- add
.gdbinitto project root directory. The content is:
python
print("Local GDB Init")
end
- add config to ~/.gdbinit:
set auto-load local-gdbinit on
set auto-load safe-path /
add-auto-load-safe-path /
python
print("Global GDB init")
end
- start gdb debugger from VSCode, it will show
Global GDB initbut noLocal GDB Init. So, project's.gdbinitnot run.
Extension version: 1.25.3
VS Code version: Code 1.100.2 (848b80aeb52026648a8ff9f7c45a9b0a80641e2e, 2025-05-14T21:47:40.416Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in a CMake project using the reported VS Code, Windows, GDB, and .gdbinit settings. Compare the global and project-local initialization behavior, then verify that the local file produces its expected output when auto-load is enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100