[Home]

Summary:ASTERISK-24403: Crashed in strncasecmp from /lib/libc.so.6 - in __get_header at chan_sip.c
Reporter:Eric H (eric.h)Labels:
Date Opened:2014-10-08 12:01:44Date Closed:2018-01-02 08:30:29.000-0600
Priority:CriticalRegression?No
Status:Closed/CompleteComponents:Channels/chan_sip/General
Versions:1.8.22.0 Frequency of
Occurrence		One Time
Related
Issues:
Environment:CentOS release 5.9 (Final)Attachments:( 0) backtrace.txt
( 1) messagelog.txt
Description:[Edit by Rusty - giant chunk of inline debug removed per the guidelines.]

{noformat}
Program terminated with signal 11, Segmentation fault.
<snip>
(gdb) bt
#0 0x00e2cfa7 in strncasecmp () from /lib/libc.so.6
#1 0x06d80c17 in __get_header (req=0xab90c2a4, name=0x6e09e5c "Via", start=0xb7c6f750) at chan_sip.c:7763
#2 0x06d8cc05 in copy_via_headers (p=0xab90ba40, req=0xb7c6fc90, orig=0xab90c2a4, field=0x6e09e5c "Via") at chan_sip.c:10425
#3 0x06d8d74b in respprep (resp=0xb7c6fc90, p=0xab90ba40, msg=0x6e07d24 "183 Session Progress", req=0xab90c2a4) at chan_sip.c:10715
#4 0x06d8eba8 in __transmit_response (p=0xab90ba40, msg=0x6e07d24 "183 Session Progress", req=0xab90c2a4, reliable=XMIT_UNRELIABLE) at chan_sip.c:10947
#5 0x06d8f53d in transmit_response (p=0xab90ba40, msg=0x6e07d24 "183 Session Progress", req=0xab90c2a4) at chan_sip.c:11083
<snip>
{noformat}
Comments:By: Rusty Newton (rnewton) 2014-10-08 12:15:20.700-0500

Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. You may find it helpful to read the Asterisk Issue Guidelines http://www.asterisk.org/developers/bug-guidelines. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need:

1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).

This likely includes output from the console with debug level logging, a SIP trace (if this is SIP related), and configuration information such as dialplan (e.g. extensions.conf) and channel configuration (e.g. sip.conf). Thanks!


By: Rusty Newton (rnewton) 2014-10-08 12:16:48.766-0500

Please read through the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] before using the tracker.

You can reattach your backtrace tas a .txt file to the issue using "More > Attach Files"

Please don't use the description or comment fields for pasting debug; as is mentioned in the guidelines.
By: Eric H (eric.h) 2014-10-08 12:23:55.587-0500

I was not doing anything. The system was simply running handling calls. No administration was occurring during this time. I was actually getting coffee during the occurrence.

The system crashed and restarted as expected.


By: Eric H (eric.h) 2014-10-08 12:45:26.150-0500

Message Log during crash ( omitted normal garbage )
By: Eric H (eric.h) 2014-10-08 12:48:13.287-0500

GDB Debug
By: Rusty Newton (rnewton) 2014-10-08 13:29:10.995-0500

Per the IRC conversation; adding a note here that a log [including DEBUG channel messages|https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information] would be very useful in investigating this further.

Also it is recommended to upgrade to the latest minor in the branch (if possible and reasonable) as with the time between 1.8.22 and 1.8.31 there may be security vulnerabilities ( you can check the commit and change logs) existing in your install.
By: Joshua C. Colp (jcolp) 2017-12-18 09:27:05.549-0600

Have you experienced this problem in current supported versions of Asterisk? (Asterisk 13 and up)
By: Asterisk Team (asteriskteam) 2018-01-02 08:30:29.508-0600

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].
[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines