[asterisk-bugs] [JIRA] (ASTERISK-29376) res_rtp_asterisk: Coredump with t.140 RED enabled

Thomas Johnson (JIRA) noreply at issues.asterisk.org
Tue Mar 30 14:07:15 CDT 2021


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

Thomas Johnson commented on ASTERISK-29376:
-------------------------------------------

Any suggestions on why I am not getting a coredump, only the log entry I posted originally.   Asterisk is run with -g

root      524458       1  0 10:27 ?        00:00:00 /bin/sh /usr/sbin/safe_asterisk -U asterisk -G asterisk
asterisk  524656    2878  0 10:27 ?        00:01:05 node /var/www/html/admin/modules/core/node/fastagi-server.js
asterisk  524892    2878  0 10:27 ?        00:01:14 letschat
asterisk  596462       1  0 14:38 ?        00:00:00 dirmngr --daemon --homedir /home/asterisk/.gnupg
asterisk  612432  524458 20 15:04 ?        00:00:09 /usr/sbin/asterisk -f -U asterisk -G asterisk -vvvg -c
asterisk  612488    2878  4 15:04 ?        00:00:02 node /var/www/html/admin/modules/ucp/node/index.js


> res_rtp_asterisk: Coredump with t.140 RED enabled
> -------------------------------------------------
>
>                 Key: ASTERISK-29376
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29376
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_rtp_asterisk
>    Affects Versions: 17.8.1
>         Environment: RedHat 8
>            Reporter: Thomas Johnson
>            Assignee: Thomas Johnson
>
> Asterisk will randomly coredump if RED is allowed.  The exception is in an apparent scheduled callback to red_write.   I tried modifying the function to check for NULL pointers, but it still crashes due to possibly an invalid pointer.



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list