Skip to content

dist: remove unused gdbinit-docker script - #22722

Open
crasbe wants to merge 1 commit into
RIOT-OS:masterfrom
crasbe:pr/remove_gdbinit-docker
Open

crasbe wants to merge 1 commit into
RIOT-OS:masterfrom
crasbe:pr/remove_gdbinit-docker

Conversation

@crasbe

@crasbe crasbe commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

Contribution description

I found this little gem while procrastinating. It does not appear to be used by anything or that it ever has been used by anything. It was added in #2392, so waaaaaay back and the last update was 8 years ago.

Testing procedure

Zero references on master:

buechse@skyleaf:~/RIOTstuff/riot-vanillaschote/RIOT$ grep -RnwIi gdbinit-docker

Issues/PRs references

None.

Declaration of AI-Tools / LLMs usage:

AI-Tools / LLMs that were used are:

  • none

@crasbe crasbe added Type: cleanup The issue proposes a clean-up / The PR cleans-up parts of the codebase / documentation CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR CI: skip compile test If set, CI server will run only non-compile jobs, but no compile jobs or their dependent jobs AI: Not Used AI was stated to not be used in this PR/Issue labels Sep 16, 2026
@riot-ci

riot-ci commented Sep 16, 2026

Copy link
Copy Markdown

Murdock results

✔️ PASSED

88643d4 dist: remove unused gdbinit-docker script

Success Failures Total Runtime
1 0 1 01m:25s

Artifacts

@crasbe
crasbe requested a review from maribu September 16, 2026 18:32
@maribu

maribu commented Sep 16, 2026

Copy link
Copy Markdown
Member

That could actually have users: You could include that from your ~/.gdbinit.

Modern GCC and clang allow to rewrite diagnostic paths, so we actually could turn all absolute paths into paths relative to the RIOT repo root. Then it wouldn't matter if an elf is built with docker or without and this script would be obsolete.

@crasbe

crasbe commented Sep 16, 2026

Copy link
Copy Markdown
Contributor Author

But does it actually still work for our docket container? And does anyone use it when there's no documentation at all?

@maribu

maribu commented Sep 16, 2026

Copy link
Copy Markdown
Member

It is only telling gdb to look up source files that the debug info says is in /data/riotbuild where the actual repo is. That shouldn't be affected by changes in the docker container other than changes to the mount paths.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AI: Not Used AI was stated to not be used in this PR/Issue CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR CI: skip compile test If set, CI server will run only non-compile jobs, but no compile jobs or their dependent jobs Type: cleanup The issue proposes a clean-up / The PR cleans-up parts of the codebase / documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants