Previously, the debug symbols were discarded by our building environment.
With this change, bluecherry-dbg packages again contain the debug symbols stripped from the built code.
Alternatively, we could change this code to "dh_strip --keep-debug" which adds 7 MB to bluecherry.deb, taking it from 28M to 35M.
The situation with instant access to crash backtraces enriched with debug symbols is now the following: the stack trace logged by bc-server itself lists the libraries for every stack frame, but not function names or line nubmers. This info is in the debug info shipped, but it is not used by glibc's backtrace() (wouldn't even if we avoid stripping overall).
Previously, the debug symbols were discarded by our building environment.
With this change, bluecherry-dbg packages again contain the debug symbols stripped from the built code.
Alternatively, we could change this code to "dh_strip --keep-debug" which adds 7 MB to bluecherry.deb, taking it from 28M to 35M.
The situation with instant access to crash backtraces enriched with debug symbols is now the following: the stack trace logged by bc-server itself lists the libraries for every stack frame, but not function names or line nubmers. This info is in the debug info shipped, but it is not used by glibc's backtrace() (wouldn't even if we avoid stripping overall).
The ways to use all the debug info are: