Summary: | ASTERISK-11377: DUNDi lookup crashes asterisk | ||
Reporter: | non-poster (non-poster) | Labels: | |
Date Opened: | 2008-02-05 00:53:27.000-0600 | Date Closed: | 2008-02-12 23:58:46.000-0600 |
Priority: | Critical | Regression? | No |
Status: | Closed/Complete | Components: | PBX/pbx_dundi |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) bt1.txt | |
Description: | Load pbx_dundi. Do "dundi lookup" from CLI. Asterisk crashes. ****** ADDITIONAL INFORMATION ****** # asterisk -r ... Connected to Asterisk 1.6.0-beta2 currently running on hostname(pid = 304) eklhq*CLI> dundi debug DUNDi Debugging Enabled eklhq*CLI> dundi lookup 847998xxxx eklhq*CLI> Disconnected from Asterisk server | ||
Comments: | By: non-poster (non-poster) 2008-02-05 00:55:04.000-0600 Works in 1.4.17 with same dundi.conf By: snuffy (snuffy) 2008-02-05 01:30:47.000-0600 Please post the backtrace for this if it is segfaulting. Guidelines for this are under doc/backtrace.txt By: snuffy (snuffy) 2008-02-05 15:10:14.000-0600 non-poster could you please see if you can replicate when you compile asterisk with 'dont optimize' that way it makes it easier to debug and you dont get the 'value has been optimised out' message when printing your bt full. By: non-poster (non-poster) 2008-02-12 23:19:13.000-0600 The patch in the related issue (11946) seems to fix this issue, eg asterisk doesn't crash when doing a dundi lookup with that patch. By: Tilghman Lesher (tilghman) 2008-02-12 23:58:46.000-0600 In that case, I'm going to close this one out as a duplicate of that issue. |