[asterisk-bugs] [JIRA] (ASTERISK-21757) segfault on asterisk startup: motif iksemel

[Matt Jordan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-21757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206199#comment-206199 ] 

Matt Jordan commented on ASTERISK-21757:
----------------------------------------

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".


                
> segfault on asterisk startup: motif iksemel
> -------------------------------------------
>
>                 Key: ASTERISK-21757
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21757
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_motif, Resources/res_xmpp
>    Affects Versions: 11.4.0
>         Environment: Fedora 17
>            Reporter: Sean Darcy
>            Assignee: Sean Darcy
>            Severity: Critical
>
> ............
>   == 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]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira