Skip to content
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

valgrind: feature request: do not strip symbols #48427

Closed
sbromberger opened this issue Jan 29, 2024 · 1 comment
Closed

valgrind: feature request: do not strip symbols #48427

sbromberger opened this issue Jan 29, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@sbromberger
Copy link
Contributor

valgrind-3.22.0_1 is installed with debug symbols stripped. This makes it impossible to submit bug reports to the valgrind team when it errors. Since valgrind handles its own errors, and having the symbols is a prerequisite for filing an issue with the upstream team, this means that a custom non-stripped binary needs to be built and used for opening up upstream issues.

(Simply using the valgrind-dbg package doesn't appear to work.)

Could this package be installed without stripping the debug symbols?

@classabbyamp classabbyamp added the bug Something isn't working label Jan 29, 2024
@classabbyamp
Copy link
Member

based on https://valgrind.org/docs/manual/dist.readme-packagers.html should probably be nostrip=yes

sbromberger added a commit to sbromberger/void-packages that referenced this issue Jan 30, 2024
Added "nostrip=yes" to preserve debug symbols, required for upstream bug submissions. Closes void-linux#48427.
sbromberger added a commit to sbromberger/void-packages that referenced this issue Jan 30, 2024
Added `nostrip=yes` to preserve debug symbols, required for upstream bug submissions. Closes void-linux#48427.
slymattz pushed a commit to slymattz/void-packages that referenced this issue Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants