I think this would make gdb manpages not show up in the Nix profile path.

you're right, I thought the propagatedBuildInput would magically do the trick when in fact we need propagatedUserEnvPkgs and then you also have to run the default builder...
Anyway, now it seems to work. Alternatively, we could also create a symlink tree with buildEnv

hm, travis seems only to fail because 'no space left on device'. Not sure why it rebuilds so much, maybe a lot of qt/kde depends on gdb.
So, this works for me now, but thinking a little more about it I think it would be better to add some hook that adds all (or some?) packages of the current build environment to the safe gdb path. The problem is that, afaik gdb doesn't read any environment variables to add safe paths. So we have to add a "-x initscript" flag to the gdb call which this wrapper does, but I don't see how we can do this depending on hooks. An alternative might be to patch gdb to include an init script that reads the safe paths from some environment variable and then just change them in the hook. I'm also not sure how this works in the "nix-env -iA gdb"/environment.systemPackages=[gdb] case.
I'm also not completely sure of the security implications of adding all buildInputs to the safe paths, but I think you trust your buildInputs anyway.
Any comments?

(triage) @fkz any update?

Just ran into #10427 again, this still needs fixing.

A quick hack if you trust your nix store would be:

# ~/.gdbinit
set auto-load safe-path /nix

Are there plans to fix and merge this? I can reproduce #10427 in 18.09, stable at aabc610.

Any update on this pull request?

Closing due to lack of activity, feel free to reopen this if needed.

Superseded by #73574.