Olivier
2017-Dec-08 17:11 UTC
[asterisk-users] Can't install package asterisk-dbgsym on Stretch
Hello, On a fresh Debian Stretch setup, I have: $ cat /etc/apt/sources.list.d//dbgsym.list deb http://debug.mirrors.debian.org/debian-debug/ stretch-debug main # apt-get update ... # apt-get install asterisk gdb # apt-get -s install asterisk-dbgsym ... asterisk-dbgsym : Depends: asterisk (= 1:13.14.1~dfsg-2+deb9u1) but 1:13.14.1~dfsg-2+deb9u2 should be installed (above output is translated from the output I had) 1. Is this a bug in debian-debug repo ? If positive, should I file a bug report ? 2. Is correct to understand that to get DONT_OPTIMZE, BETTER_BACKTRACE and so on options compiled in, I must recompile anyway ? Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20171208/efc7ee73/attachment.html>
Daniel Tryba
2017-Dec-10 18:42 UTC
[asterisk-users] Can't install package asterisk-dbgsym on Stretch
On Fri, Dec 08, 2017 at 06:11:47PM +0100, Olivier wrote:> 1. Is this a bug in debian-debug repo ? If positive, should I file a bug > report ? > > 2. Is correct to understand that to get DONT_OPTIMZE, BETTER_BACKTRACE and > so on options compiled in, I must recompile anyway ?As far as I know the deb debug package just contains debugging symbols (before these are stripped), you still need the normal asterisk packages with the binaries. The last time I tried to debug with these packages it was a waste of time since your not running a version with debugging options. These debug packages show some extra info in gdb traces, but lots of important stuff is still optimized away. If you need to debug install the source package and compile from there. You might want to figure out how to manipulate the deb build rules to include wanted flags, shouldn't be to hard but it has been a few years for myself.
Tzafrir Cohen
2017-Dec-14 15:28 UTC
[asterisk-users] Can't install package asterisk-dbgsym on Stretch
On Fri, Dec 08, 2017 at 06:11:47PM +0100, Olivier wrote:> Hello, > > On a fresh Debian Stretch setup, I have: > $ cat /etc/apt/sources.list.d//dbgsym.list > deb http://debug.mirrors.debian.org/debian-debug/ stretch-debug main > > # apt-get update > ... > # apt-get install asterisk gdb > > # apt-get -s install asterisk-dbgsym > ... > asterisk-dbgsym : Depends: asterisk (= 1:13.14.1~dfsg-2+deb9u1) but > 1:13.14.1~dfsg-2+deb9u2 should be installedYou seem to mix two versions. apt-cache policy asterisk apt-cache policy asterisk-dbgsym> > (above output is translated from the output I had)(Hint: LC_ALL=C <original command line>)> > > 1. Is this a bug in debian-debug repo ? If positive, should I file a bug > report ?rmadison shows me now that the versions of asterisk is 1:13.14.1~dfsg-2+deb9u2 in both the stable and the stable-debug repos.> > 2. Is correct to understand that to get DONT_OPTIMZE, BETTER_BACKTRACE and > so on options compiled in, I must recompile anyway ?Right. DONT_OPTIMZE has a considerable performance impact. I never considered BETTER_BACKTRACE and its performance impact. Is it independent of DONT_OPTIMZE? -- Tzafrir Cohen +972-50-7952406 mailto:tzafrir.cohen at xorcom.com http://www.xorcom.com