Summary: | ASTERISK-11220: misdn reload break with glibc detected | ||
Reporter: | waxman (waxman) | Labels: | |
Date Opened: | 2008-01-12 10:15:35.000-0600 | Date Closed: | 2011-06-07 14:01:08 |
Priority: | Critical | Regression? | No |
Status: | Closed/Complete | Components: | Channels/chan_misdn |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) output.txt | |
Description: | As soon as I write the ports= setting in the misdn.conf and then try to reload the configurationparams for the running asteriskserver with misdn reload I get the following error msg: *CLI> misdn reload Reloading mISDN Config == Parsing '/etc/asterisk/misdn.conf': Found *** glibc detected *** double free or corruption (fasttop): 0x0819f4b0 *** Abgebrochen ****** ADDITIONAL INFORMATION ****** My misdn.conf looks like [default] ports=1 context=misdn language=de senddtmf=yes hold_allowed=yes msns=* ######################## i have the latest mISDN and mISDNuser installed on to a debian 4.0 system with an avmfritz card | ||
Comments: | By: waxman (waxman) 2008-01-12 10:58:11.000-0600 I'm not a C/C++ programmer, so that I can't support you with a gdb traceback or similar, but if someone could explain me how to do so, I would create an traceback. Additionally I compiled the newest version (1.4.17) but the failure still exists with this version. By: snuffy (snuffy) 2008-01-12 14:37:20.000-0600 waxman. post the results following 'doc/backtrace.txt' under the asterisk source directory By: waxman (waxman) 2008-01-13 02:27:29.000-0600 snuffy, thanks for the hint to the helpfile in the documentation. It seems that I oversaw that file. Anyway, I attached the gdb output like it is written in the file. By: Jason Parker (jparker) 2008-01-29 18:16:04.000-0600 I wonder if this is related to ASTERISK-11319, which was fixed earlier today. Could you try the latest 1.4 svn, and see if it helps at all? By: Brandon Kruse (bkruse) 2008-01-30 20:20:46.000-0600 If updating does not fix it, recompile with DONT_OPTIMIZE in menuselect under compiler fags and reattach the crash (if this is not already a DONT_OPTIMIZE crash) By: jmls (jmls) 2008-05-03 14:20:26 closed because of lack of feedback. Please reopen if still an issue with the latest 1.4 |