News for hackers. Stuff that matters.
Re:Debug Information Is Huge and What to Do About It by jquast on Monday October 30, 2017 @07:13PM (#15589826)
Please Arch Linux developers: stop stripping all packages of debug symbols
Re:Debug Information Is Huge and What to Do About It by voltagex_ on Monday October 30, 2017 @09:14PM (#15590427)
Re:Debug Information Is Huge and What to Do About It by codys on Monday October 30, 2017 @09:21PM (#15590453)
If you build packages yourself, one can either include debug info, or generate a split package that includes debug info.

The piece that may still be missing is the inclusion of source code in debug packages, which is necessary to get any context for a debug session (it is not sufficient to seek out and clone random git repos because of versioning & patching differences).

But ideally, there would be a `-debug` package for every package in arch's repos, and one would not need to build them manually when debug symbols are needed. Arch does not have this.

Re:Debug Information Is Huge and What to Do About It by d33 on Monday October 30, 2017 @07:14PM (#15589834)
Isn't it a common practice to strip, but keep them in separately published files that only contain symbols?
Re:Debug Information Is Huge and What to Do About It by codys on Monday October 30, 2017 @09:22PM (#15590459)
It is, in linux distros at large. Arch, however, does not publish (or even generate) those debug files (which contain the debug info & symbols that were stripped out).
Re:Debug Information Is Huge and What to Do About It by cozzyd on Monday October 30, 2017 @07:26PM (#15589907)
That's how Fedora/EL does it at least. GDB even tells you what debug info packages are missing