Hi Tavis, please see the reply from the tracker.
regards, bogdan Tavis P wrote:
I've found a reproduceable segmentation fault during a simple call forward busy scenario: 1. Terminating caller receives INVITE 2. Responds busy, OpenSER catches the 487 and re-executes several routing blocks 3. During a simple operation in one of these routing blocks (checking a flag i believe) OpenSER is terminated with a signal 11 and dumps core Below is a gdb backtrace (bt, and bt full. in order) of the core file Please let me know if you need any more information This was reproduced on Openser rel 1_0_0, checked out of CVS this morning
_______________________________________________ Devel mailing list [email protected] http://openser.org/cgi-bin/mailman/listinfo/devel
