Summary: | ASTERISK-06970: Asterisk crash in sip_alloc at chan_sip.c:3038 | ||
Reporter: | wILMAR cAMPOS (willcampos) | Labels: | |
Date Opened: | 2006-05-13 10:13:24 | Date Closed: | 2006-05-25 20:45:32 |
Priority: | Critical | Regression? | No |
Status: | Closed/Complete | Components: | Core/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | Yesterday asterisk begin to crash continously for about 2 hours, here i post the gdb asterisk core.* that shows the crash. ****** ADDITIONAL INFORMATION ****** #0 0x4017fffe in malloc_consolidate () from /lib/libc.so.6 No symbol table info available. #1 0x4017f703 in _int_malloc () from /lib/libc.so.6 No symbol table info available. #2 0x4017f080 in calloc () from /lib/libc.so.6 No symbol table info available. #3 0x406c2f12 in sip_alloc (callid=0xbe1febb8 "d80dffffc8feffff@192.168.40.100", sin=0xbe1fe7a4, useglobal_nat=1, intended_method=2) at chan_sip.c:3038 p = (struct sip_pvt *) 0xbe1fe7a4 #4 0x406d73b9 in find_call (req=0xbe1fe7b4, sin=0x812e018, intended_method=135454744) at chan_sip.c:3195 found = 1081035376 p = (struct sip_pvt *) 0xbe1febb8 callid = 0xbe1febb8 "d80dffffc8feffff@192.168.40.100" tag = 0x406ea331 "" totag = '\0' <repeats 56 times>, "ûÓ\002@ô_#@\234æ\037¾¸Ó\002@¼æ\037¾ÏV\030@pÞ\002@ûÓ\002@ô_#\000$Do@\030\000\000\000\002\000\000\000àû\037¾ô/\003@àû\037¾\210Jo@ìæ\037¾ª\002@" fromtag = '\0' <repeats 127 times> ASTERISK-1 0x406d5aa7 in sipsock_read (id=0x81703e8, fd=18, events=1, ignore=0x0) at chan_sip.c:11151 req = {rlPart1 = 0xbe1fe9cc "REGISTER", rlPart2 = 0xbe1fe9d5 "sip:sipserver", len = 705, headers = 13, method = 2, header = {0xbe1fe9cc "REGISTER", 0xbe1fe9f4 "Via: SIP/2.0/UDP 192.168.40.100:5062;branch=z9hG4bK2af9ffff5deeffff", 0xbe1fea39 "From: \"Luis FXO House\" <sip:17000000002@sipserver;user=phone>;tag=0ca300000ccfffff", 0xbe1fea95 "To: <sip:17000000002@sipserver;user=phone>", 0xbe1feac9 "Contact: <sip:17000000002@192.168.40.100:5062;user=phone>", 0xbe1feb04 "Authorization: Digest username=\"17000000002\", realm=\"asterisk\", algorithm=MD5, uri=\"sip:sip.voip2talk.net\", nonce=\"4f9c19f9\", response=\"1464111d85216bc20148389bd69df4b5\"", 0xbe1febaf "Call-ID: d80dffffc8feffff@192.168.40.100", 0xbe1febd9 "CSeq: 3888 REGISTER", 0xbe1febee "Expires: 180", 0xbe1febfc "User-Agent: Grandstream HT488 1.0.2.16", 0xbe1fec24 "Max-Forwards: 70", 0xbe1fec36 "Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE", 0xbe1fec78 "Content-Length: 0", 0xbe1fec8b "", 0x0 <repeats 50 times>}, lines = 0, line = {0xbe1fec8d "", 0x0 <repeats 63 times>}, data = "REGISTER\000sip:sipserver\000SIP/2.0\000\000Via: SIP/2.0/UDP 192.168.40.100:5062;branch=z9hG4bK2af9ffff5deeffff\000\000From: \"Luis FXO House\" <sip:17000000002@sipserver;user=phone>;tag=0ca300000ccfffff\000"..., debug = 0, flags = 0} sin = {sin_family = 2, sin_port = 50707, sin_addr = {s_addr = 61597976}, sin_zero = "\000\000\000\000\000\000\000"} p = (struct sip_pvt *) 0xbe1fe7b4 res = 2 len = 16 nounlock = 0 recount = 0 iabuf = '\0' <repeats 15 times> ASTERISK-2 0x080558cd in ast_io_wait (ioc=0x816b0b8, howlong=135454744) at io.c:284 res = 1 x = 0 | ||
Comments: | By: Andrey S Pankov (casper) 2006-05-14 15:49:09 Could you give some details on distro/platform/gcc version? By: wILMAR cAMPOS (willcampos) 2006-05-14 16:48:36 Reading specs from /usr/lib/gcc-lib/i486-slackware-linux/3.3.4/specs Configured with: ../gcc-3.3.4/configure --prefix=/usr --enable-shared --enable-threads=posix --enable-__cxa_atexit --disable-checking --with-gnu-ld --verbose --target=i486-slackware-linux --host=i486-slackware-linux Thread model: posix gcc version 3.3.4 Asterisk 1.2.7.1 Slackware 10.1 kernel 2.4 Anything else let me know please. Thanks, By: Andrey S Pankov (casper) 2006-05-15 16:02:33 Please add a relation to ASTERISK-6751. They are really the same bug. By: Serge Vecher (serge-v) 2006-05-19 16:45:16 any code modifications or this is straight from the tarball? By: wILMAR cAMPOS (willcampos) 2006-05-25 20:35:03 No code modifications. Unfourtunely asterisk has not crash anymore, so I cannot get the core.dump. By: Serge Vecher (serge-v) 2006-05-25 20:45:14 willcampos: unfortunately? no - very fortunately :) I will close this issue for now. If, in the future, you get this happen again, please try a solution posted by tkarlic in 6831 and report back if that remedies the situation. Thanks very much and good luck! |