[Home]

Summary:ASTERISK-21757: segfault on asterisk startup: motif iksemel
Reporter:Sean Darcy (seandarcy)Labels:
Date Opened:2013-05-04 22:14:04Date Closed:2013-05-21 09:09:07
Priority:CriticalRegression?Yes
Status:Closed/CompleteComponents:Channels/chan_motif Resources/res_xmpp
Versions:11.4.0 Frequency of
Occurrence		Constant
Related
Issues:
Environment:Fedora 17Attachments:
Description:............
 == Registered channel type 'MulticastRTP' (Multicast RTP Paging Channel Driver)
chan_multicast_rtp.so => (Multicast RTP Paging Channel)
 == Parsing '/etc/asterisk/motif.conf': Found
Segmentation fault

/var/log/messages:

kernel: [ 3085.418571] asterisk[23965]: segfault at 0 ip 00007fae2d2e722d sp 00007fffe9d2adc0 error 4 in libiksemel.so.3.1.1[7fae2d2de000+d000]
Comments:By: Sean Darcy (seandarcy) 2013-05-05 09:29:13.434-0500

Forgot:
iksemel-1.4-4.fc17.x86_64

I've rebuilt both iksemel and asterisk-1.11.4-rc1. No build errors.
By: Matt Jordan (mjordan) 2013-05-05 09:43:43.784-0500

Thank you for your bug report. In order to move your issue forward, we require a backtrace[1] from the core file produced after the crash. Also, be sure you have DONT_OPTIMIZE enabled in menuselect within the Compiler Flags section, then:

make install

After enabling, reproduce the crash, and then execute the backtrace[1] instructions. When complete, attach that file to this issue report.

[1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace


By: Sean Darcy (seandarcy) 2013-05-08 10:29:47.583-0500

I've figured out what caused the segfault: google started requiring a captcha for one of accounts. Straightened that out, and no segfault.

But a problem still remains: we shouldn't segfault just because one of the xmpp accounts can't connect. That's like segfaulting if a sip register fails.

Now there may be nothing to be done, since iksemel itself segfaults. I posted a bug on the iksemel site, but there hasn't been any activity for over 2 years.

Can asterisk somehow trap this segfault and return a warning?

By: Matt Jordan (mjordan) 2013-05-08 11:22:38.673-0500

That would probably be a bad idea. Catching SIGSEGV is... wrong.

A backtrace would still help. It's possible that Asterisk was presenting iksemel with the bad data, and we could provide better sanitization of parameters before handing it off to the lower level library. That would prevent the seg fault without resorting to what can only be charitably described as "shenanigans".


By: Matt Jordan (mjordan) 2013-05-21 09:09:00.176-0500

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.  Further information can be found at http://www.asterisk.org/developers/bug-guidelines