There isn't any useful information in the most recent core file
backtraces. I'm rebuilding 1.5.5 with the mode=debug option so that
more information will be available next time (if there is a next time).
Thanks
Stagg
On 12/3/10 5:57 AM, Daniel-Constantin Mierla wrote:
Hello,
probably is so
I take it back, 1.5.5 just crashed. I'll get the backtrace
information and will post it here.
Thanks
Stagg
On 12/3/10 5:57 AM, Daniel-Constantin Mierla wrote:
Hello,
probably is something triggered by a new kind of SIP message which was
not encountered before, since there were no changes i
Daniel,
Thank you for the reply back. Unfortunately for the diagnosis with
version 1.5.4-notls we had already upgraded to version 1.5.5-notls and
the core files had been deleted before receiving your reply. I can
state that version 1.5.5-notls has not exhibited the issue that we
experience
Hello,
probably is something triggered by a new kind of SIP message which was
not encountered before, since there were no changes in that code. Can
you send the output of 'bt full' in gdb?
Also, you should have the content of SIP request/reply available in core
file, in one of gdb frames. Pl
Kamailio 1.5.4 segmentation faulted today. I was able to determine
with gdb that the error occurred at mediaproxy.c line 1104. Line 1104
is a call to memcpy
Core was generated by `/sbin/kamailio -m 512'.
Program terminated with signal 11, Segmentation fault.
#0 0x7f1469db6bb5 in replace
