Hello,
the patch will be on 4.1.4.
Can you give the 'bt full' for the new coredump file?
Also, locate where is variable 't' available in a frame and do in that frame:
set print elements 2000 p *t p *t->uas.request
Cheers, Daniel
On 09/06/14 10:14, Igor Potjevlesch wrote:
Hello Daniel,
New occurrence happened on Saturday.
I got the following information according to your previous email:
(gdb) p *msg->pai
$2 = {type = HDR_PAI_T, name = {
s = 0x7f6a60cd34b8 "P-Asserted-Identity: "0123456789"sip:0123456789@A.B.C.D\r\nContact: sip:0123456789@A.B.C.D:5060\r\nAllow: INVITE, BYE, REGISTER, ACK, OPTIONS, CANCEL, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE\r\nSupported: path, replaces, timer, tdialog\r\nSession-Expires: 1800\r\nExpires: 300\r\nOrganization: Dialogic\r\nContent-Type: application/sdp\r\nContent-Length: 303\r\n\r\nv=0\r\no=Dialogic_SDP 14338449 0 IN IP4 A.B.C.D\r\ns=Dialogic-SIP\r\nc=IN IP4 A.B.C.D\r\nt=0 0\r\nm=audio 8708 RTP/AVP 8 0 18 101\r\na=rtpmap:0 PCMU/8000\r\na=rtpmap:8 PCMA/8000\r\na=rtpmap:18 G729/8000\r\na=fmtp:18 annexb=yes\r\na=rtpmap:101 telephone-event/8000\r\na=fmtp:101 0-15\r\na=silenceSupp:off - - - -\r\n", len = 19}, body = {
s = 0x7f6a60cd34cd ""0123456789"sip:0123456789@A.B.C.D\r\nContact: sip:0123456789@A.B.C.D:5060\r\nAllow: INVITE, BYE, REGISTER, ACK, OPTIONS, CANCEL, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE\r\nSupported: path, replaces, timer, tdialog\r\nSession-Expires: 1800\r\nExpires: 300\r\nOrganization: Dialogic\r\nContent-Type: application/sdp\r\nContent-Length: 303\r\n\r\nv=0\r\no=Dialogic_SDP 14338449 0 IN IP4 A.B.C.D\r\ns=Dialogic-SIP\r\nc=IN IP4 A.B.C.D\r\nt=0 0\r\nm=audio 8708 RTP/AVP 8 0 18 101\r\na=rtpmap:0 PCMU/8000\r\na=rtpmap:8 PCMA/8000\r\na=rtpmap:18 G729/8000\r\na=fmtp:18 annexb=yes\r\na=rtpmap:101 telephone-event/8000\r\na=fmtp:101 0-15\r\na=silenceSupp:off - - - -\r\n", len = 43}, len = 66, parsed = 0x7f6a6d81da88, next = 0x7f6a60cd3f10}
(gdb) p *((p_id_body_t*)msg->pai->parsed)
$3 = {id = 0x0, num_ids = 0, next = 0x0}
(gdb)
I still not patched. Do you schedule to include the patch in 4.1.4?
Do you need more information?
Regards,
Igor.
*De :*Daniel-Constantin Mierla [mailto:miconda@gmail.com mailto:miconda@gmail.com] *Envoyé :* vendredi 30 mai 2014 18:02 *À :* Igor Potjevlesch; Kamailio (SER) - Users Mailing List *Objet :* Re: [SR-Users] Crash Kamailio 4.1.3
Hello,
On 30/05/14 17:41, Igor Potjevlesch wrote:
Hello, The crash happen once. it can't be reproduced. The pai seems good, why it cannot be parsed?apparently it was parsed, but then the content got reset. The sip_msg_t for request is accessed via a callback inside acc module when the sip_msg_t for response is handled.
So I have to see why it got reset, it shouldn't -- the patch so far was to prevent the crash.
Cheers, Daniel
Regards, Igor. 2014-05-29 17:11 GMT+02:00 Daniel-Constantin Mierla <miconda@gmail.com <mailto:miconda@gmail.com>>: Hello, for the moment I added a safety check to prevent crash in such situation: - http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=e633ca6b7e748a77825d3208e86bf9bce18944a5 I need to investigate more to discover why the parsed field has null content. Does the crash happen often or can it be reproduced? Cheers, Daniel On 29/05/14 10:18, Daniel-Constantin Mierla wrote: Hello, I missed somehow the message with the pai parsed content. I will look over it later today. Cheers, Daniel On 28/05/14 18:45, Igor Potjevlesch wrote: Hello, Do you any ideas about the reason of this issue? Is it caused by the last call? Do you have enough information with the PAI? Regards, Igor. 2014-05-28 13:47 GMT+02:00 Igor Potjevlesch <igor.potjevlesch@gmail.com <mailto:igor.potjevlesch@gmail.com>>: Hello, p *msg->pai : $4 = {type = HDR_PAI_T, name = { s = 0x7fad2cf8af74 "P-Asserted-Identity: \"0123456789\"<sip:0123456789@a.b.c.d>\r\nContent-Type: application/sdp\r\nContent-Length: 298\r\n\r\nv=0\r\no=root 1751857229 1751857230 IN IP4 a.b.c.d\r\ns=Asterisk PBX 1.6.2.9-2+squeeze3\r\nc=IN IP4 a.b.c.d\r\nt=0 0\r\nm=audio 11886 RTP/AVP 8 3 0 101\r\na=rtpmap:8 PCMA/8000\r\na=rtpmap:3 GSM/8000\r\na=rtpmap:0 PCMU/8000\r\na=rtpmap:101 telephone-event/8000\r\na=fmtp:101 0-16\r\na=ptime:20\r\na=sendrecv\r\n", len = 19}, body = { s = 0x7fad2cf8af89 "\"0123456789\"<sip:0123456789@a.b.c.d>\r\nContent-Type: application/sdp\r\nContent-Length: 298\r\n\r\nv=0\r\no=root 1751857229 1751857230 IN IP4 a.b.c.d\r\ns=Asterisk PBX 1.6.2.9-2+squeeze3\r\nc=IN IP4 a.b.c.d\r\nt=0 0\r\nm=audio 11886 RTP/AVP 8 3 0 101\r\na=rtpmap:8 PCMA/8000\r\na=rtpmap:3 GSM/8000\r\na=rtpmap:0 PCMU/8000\r\na=rtpmap:101 telephone-event/8000\r\na=fmtp:101 0-16\r\na=ptime:20\r\na=sendrecv\r\n", len = 43}, len = 66, parsed = 0x7fad389a7220, next = 0x7fad2cf8baf0} p *((p_id_body_t*)msg->pai->parsed) : $5 = {id = 0x0, num_ids = 0, next = 0x0} Regards, Igor. 2014-05-28 13:29 GMT+02:00 Daniel-Constantin Mierla <miconda@gmail.com <mailto:miconda@gmail.com>>: Hello, I need now: p *msg->pai p *((p_id_body_t*)msg->pai->parsed) Cheers, Daniel -- Daniel-Constantin Mierla -http://www.asipto.com http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> -http://www.linkedin.com/in/miconda -- Daniel-Constantin Mierla -http://www.asipto.com http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> -http://www.linkedin.com/in/miconda-- Daniel-Constantin Mierla -http://www.asipto.com http://twitter.com/#!/miconda http://twitter.com/#%21/miconda -http://www.linkedin.com/in/miconda