Improving debugging support for Asterisk

[Tzafrir Cohen]

Hi,

On Thu, Apr 07, 2011 at 07:48:48PM -0400, Paul Belanger wrote:
> Evening,
>
> Currently, we don't have a good method to generate unoptimized  
> backtraces if Asterisk crashes; this make it hard for upstream developer  
> to get the required information.  With this patch, we now toggle  
> --enable-dev-mode, DONT_OPTIMIZE and DEBUG_THREADS, the usually flags  
> required to generate a backtrace[1].
>
> This does not affect packages in the repository (because of the overhead  
> added to Asterisk), but allows local users to rebuild the package if  
> required.
>
> $ sudo apt-get build-dep asterisk
> $ DEB_BUILD_OPTIONS="debug" apt-get -b source asterisk
>
> Once built, the local user can install, reproduce their issue, and  
> generate a good backtrace.
>
> [1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace

Looks good.

One minor commet:

> Index: debian/patches/hack-multiple-app-voicemail
> ===================================================================
> --- debian/patches/hack-multiple-app-voicemail	(revision 8844)
> +++ debian/patches/hack-multiple-app-voicemail	(working copy)
> @@ -41,7 +41,7 @@
>  +	$(call add_depends_cmd,unixodbc) $@
>  +	$(call add_depends_cmd,ltdl) $@
>  +
> -+clean::
> ++dist-clean::

Why? Is that change related?

>  +	rm -f app_voicemail_*.c
>  +
>  +app_voicemail_imapstorage.o: _ASTCFLAGS+=-DIMAP_STORAGE

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir