On 07.11.2020 12:25, M S wrote:
I am using opensips 3.1.0:
Any ideas what caused it?
Hi, Mark!
Could you install the "opensips-dbg" package and re-post the backtrace?
Thanks to the debug symbols, the information provided should be much richer.
Also, if you're pushing less than 100 calls-per-second through that
machine, then I recommend starting OpenSIPS with the "-a Q_MALLOC_DBG"
command-line option and post the new backtrace, when the crash
re-occurs. This quality assurance allocator contains extra runtime
checks and it may detect the problem in some earlier, more relevant
place in the code, as the bug occurs.
PS: to obtain a quality backtrace using `gdb` and not that garbled wall
of text from systemd, see this tutorial [1]
[1]: https://www.opensips.org/Documentation/TroubleShooting-Crash
--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
