| Summary: | ASTERISK-09338: CHANNEL function causes segfault | ||
| Reporter: | John Todd (jtodd) | Labels: | |
| Date Opened: | 2007-04-27 17:11:27 | Date Closed: | 2007-07-11 19:58:41 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/RTP |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) 20070427__bug9619.diff.txt ( 1) rtpqos-bt.txt | |
| Description: | exten => 1,n,NoOp(Channel data: ${CHANNEL(rtpqos,audio)}) causes a core dump. While this may not even be the correct syntax, the error condition should not be a segfault. Backtrace included. ****** ADDITIONAL INFORMATION ****** exten => 1,1,Answer exten => 1,n,NoOp(${CHANNEL}) exten => 1,n(monkeys),Playback(tt-monkeys) exten => 1,n,NoOp(Channel data: ${CHANNEL(rtpqos,audio)}) results in this: *CLI> -- Executing [1@from-jt:1] Answer("SIP/2208-08b70bf0", "") in new stack -- Executing [1@from-jt:2] NoOp("SIP/2208-08b70bf0", "SIP/2208-08b70bf0") in new stack -- Executing [1@from-jt:3] Playback("SIP/2208-08b70bf0", "tt-monkeys") in new stack -- <SIP/2208-08b70bf0> Playing 'tt-monkeys.ulaw' (language 'en') Segmentation fault (core dumped) | ||
| Comments: | By: Jason Parker (jparker) 2007-04-27 18:01:36 backtrace is unreadable - at least on this machine. Could you double-check the formatting? By: Tilghman Lesher (tilghman) 2007-04-29 18:46:16 Patch attached; please test. By: Russell Bryant (russell) 2007-04-30 10:37:16 This issue has been resolved in trunk in revision 62416, thanks! | ||