<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2017-02-17 14:39 GMT+01:00 George Joseph <span dir="ltr"><<a target="_blank" href="mailto:gjoseph@digium.com">gjoseph@digium.com</a>></span>:<br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><span class="gmail-"></span><br><div><br></div><div>If asterisk was compiled with DEBUG_THREADS,<br></div></div></div></div></blockquote><div><br></div><div>Would you then  advise to run an Asterisk server in production with DEBUG_THREADS enabled ?<br></div><div>Page [1] does not mention to do so nor to avoid it.<br><br></div><div>In the production environment I'm thinking about, Asterisk is compiled with DONT_OPTIMIZE and BETTER_BACKTRACES<br></div><div>hoping that if Asterisk ever fails, sysadmins would have everything needed to track the issue no matter if those would increase resources needed to run Asterisk properly.<br><br></div><div><br></div></div>[1] <a href="https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace#GettingaBacktrace-GettingInformationForADeadlock">https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace#GettingaBacktrace-GettingInformationForADeadlock</a><br></div></div>