Re-add separateDebugInfo = true; once the GDB bugfix is rolled out everywhere #1003
Labels
No labels
Affects/CppNix
Affects/Nightly
Affects/Only nightly
Affects/Stable
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/lix ci
Area/nix-eval-jobs
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/repl/debugger
Area/store
awaiting
author
awaiting
contributors
bug
Context
contributors
Context
drive-by
Context
maintainers
Context
RFD
crash 💥
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
Feature/S3
imported
Language/Bash
Language/C++
Language/NixLang
Language/Python
Language/Rust
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
Topic/Large Scale Installations
ux
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lix-project/lix#1003
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Describe the bug
Not a real bug, but I figured having an issue for documentation purposes is still sensible.
In https://gerrit.lix.systems/c/lix/+/3880 we had to turn off
separateDebugInfo = true;since this resulted in the debug script not being loaded.The reason is that the hook for
separateDebugInfo=true;also turns on compression for these sections, but the code-path in GDB for loading user scripts regressed on loading compressed scripts recently.I filed a patch for binutils-gdb: https://sourceware.org/pipermail/gdb-patches/2025-October/221398.html
Once it's available for nixpkgs, we should turn
separateDebugInfofor Linux back on.Additional context
Add any other context about the problem here.
has the upstream bug been fixed yet?
Yes, but it's not released yet. They missed pulling our commit for the last gdb release for no apparent reason.
fwiw, I'm keeping an eye on upstream releases currently (also because I'm awaiting the test-case they sniped me into writing to be merged :D)
The patch got now backported to the 17.x branch, so it will be part of gdb 17.2: https://sourceware.org/bugzilla/show_bug.cgi?id=33768, https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=0926b8b8339ce5aacd564dd319a284375e4861db