[Asterisk-Users] Realtime Problem = Segmentation faults Seems to be asterisk

[Jose R. Ortiz Ubarri]

Jose R. Ortiz wrote:

> Greg Boehnlein wrote:
>
>> On Fri, 18 Mar 2005, Jose R. Ortiz Ubarri wrote:
>>
>>  
>>
>>> Jose R. Ortiz Ubarri wrote:
>>>
>>>   
>>>
>>>> Hi:
>>>>   I had asterisk with RealTime database working perfectly in a RH 
>>>> 9.0 machine.  I used the sip cache so I even had MWI working.  The 
>>>> problem is that I decided to move to Fedora Core 3.  I installed 
>>>> the lastets cvs version of asterisk and the RealTime addon from 
>>>> asterisk-addons.  I at first had the problems with the kernel and 
>>>> the zaptel driver but all that was solved with the configuration 
>>>> from the Asterisk Wiki.  Then when I moved my configuration to the 
>>>> new asterisk server and configured the RealTime addon it falls in a 
>>>> Segmentation fault.  If I do not load the res_config_mysql.so 
>>>> (edited at modules.conf) then asterisks runs without any problem.  
>>>> But if I load the module from boot or from the asterisk command 
>>>> load res_config_mysql.so then I get the Segmentation fault again.
>>>>
>>>> I'm not sure what the problem is.  Is it a Fedora Core 3 problem, 
>>>> or an Asterisk latest version problem?
>>>> I don't think it is a configuration problem because I just used the 
>>>> same configuration I had before.  The only diferences may be the OS 
>>>> and probably the asterisk version that is only one week newer than 
>>>> the one I was running in the old asterisk server, so I'm probably 
>>>> even running the same version of asterisk in both machines.
>>>>
>>>> Any advise?  Someone else have a similar configuration working with 
>>>> Fedora Core 3?
>>>>
>>>> Thanks in advance,
>>>>     
>>>
>>> Debugging the code and as you can see in the backtrace the problem 
>>> is that it is receiving a Null variable (name) and then making the 
>>> comparison.  Is it an asterisk bug?  What asterisk should do if the 
>>> variable name received is NULL?
>>>   
>>
>>
>> Has this been entered into the Bug Tracker? If so, what bug number 
>> was it assigned?
>>
> The bug id is 0003814.  I jumped the category drop down and it says to 
> be a Codec Handling Problem.  I couldn't edit it...
>
> -- 
> JO
>
>
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users

This bug is fixed in the CVS Head

-- 
Jose R. Ortiz Ubarri (CHEO), CS
System Administrator / Programmer
High Performance Computing facility - UPR
Email: Jose.Ortiz at hpcf.upr.edu|cheo at hpcf.upr.edu
Phone: 787-758-3054
Fax: 787-758-3058