Hello,
I see port is 5060, is it a possibility that you have multiplexing of websocket or other protocol (http, msrp) there?
Can you also give the locals?
frame 0
info locals
Cheers,
Daniel
On 05.06.17 05:19, Armen Babikyan wrote:
Hello,
Over the past few months, I've seen a smattering of kamailio crashes on various systems with identical backtraces: SIGSEGV in tcp_read_headers(), at tcp_read.c line 628. Example here:
Note that in frame 0, print *c shows that req->parsed is pointing to an address exactly 8GB lower than req->buf. That req->parsed is pointing to an invalid memory location, crashing kamailio when the location is dereferenced. In other coredumps, I see that req->parsed is pointing to an address exactly 4GB lower than req->buf.
Other info: This is Kamailio 4.4.4 on x86_64. I've not had success trying to reproduce this yet. Also worth noting that the crashes seem to be consistently associated with processing traffic from a UA connected over SIP/TCP; I've seen no other transport associated with this crash.
Thoughts are welcome. Thanks!
Armen
_______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/ cgi-bin/mailman/listinfo/sr- users
-- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - www.kamailioworld.com
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr- users