On 14 December 2011 12:56, Paulo Santos <paulo.r.san...@sapo.pt> wrote: > Hello list, > > An Asterisk installation that was doing fine suddenly stared segfaulting a > couple of times per day. I enabled all the logging and debugging to try to > find a pattern but there was too much information to see exactly where it > broke. So I enabled core dump and did backtraces and all of them seem to > break on ast_setstate, setting the state to AST_STATE_DOWN. That's pretty > much the only thing I can make of it, don't even know if that's correct. > > Does anyone have any ideas on why this is happening? The backtrace is > attached. > > P.S.: I've switched the whole hardware already, including the BRI card > (B400P, OpenVox). Also tried different versions of Asterisk, Dahdi and > mISDN. I'm stuck with 1.4 Asterisk branch and mISDN v1. >
If I was guessing, I'd say that the channel structure that is being modified by the ast_setstate() call is incomplete, and contains some garbage pointers. If I was guessing further, I'd say that the callerID pointers are the most likely candidate - Does the issue happen when a caller-id withheld call is hung-up? hung-up before being answered perhaps? You'd need to add some debug reporting into ast_setstate() to know for sure. Just my 2p - 1.4.42 is an old version, so the chance of a solid answer is fairly low. Steve -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
