-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/3765/
-----------------------------------------------------------

(Updated July 18, 2014, 12:55 p.m.)


Status
------

This change has been marked as submitted.


Review request for Asterisk Developers.


Changes
-------

Committed in revision 418963


Repository: Asterisk


Description
-------

On an invalid refcount, rather than just log the message and continue executing 
normally, provide a backtrace and an assert to stop on DO_CRASH.  This can help 
to catch the first case of an invalid refcount rather than being distracted 
from the problem with a flurry additional logs from other threads encountering 
already mangled data.


Diffs
-----

  /trunk/main/utils.c 418910 
  /trunk/main/logger.c 418910 
  /trunk/main/astobj2.c 418910 
  /trunk/include/asterisk/astobj2.h 418910 

Diff: https://reviewboard.asterisk.org/r/3765/diff/


Testing
-------


Thanks,

Scott Griepentrog

-- 
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

Reply via email to