[Asterisk-Dev] SEGV in CVS version of Asterisk

[Steven Critchfield]

On Wed, 2003-12-10 at 09:58, Jonathan Tew wrote:
> I would have to disagree with the advice that you guys are giving this 
> person.  If the module compiles in to Asterisk by default then it should 
> be coded to handle the null pointer gracefully.  Other non-developers 
> could experience the same crashing of Asterisk and have no idea what is 
> going on or how to diagnose it.  All they end up doing is either stop 
> using the product because it seems buggy or harass people over and over 
> again on the users mailing list.

While you are right that the bug shouldn't exist, his first need was to
get the software up. So there needed to be a two prong approach here.
One being get this user using the software, and secondly getting the
code able to handle this kind of situation. I was only able to help with
getting the software started as I do not know anything about the channel
driver in question. Later the people with the proper knowledge can solve
that issue.

> Matteo Brancaleoni wrote:
> 
> >or better, just rm -fR all modules you don't need
> >in /usr/lib/asterisk/modules 
> >so no need to bother 'bout modules.conf
> >
> >but be aware that there're some deps between them
> >(ie. can't have chan_modem_blah without chan_modem.so)
> >
> >Matteo.
> >
> >Il mer, 2003-12-10 alle 05:48, Steven Critchfield ha scritto:
> >  
> >
> >>in /etc/asterisk/modules.conf
> >>
> >>noload=>chan_vbp.so
> >>
> >>On Tue, 2003-12-09 at 21:53, Ron OHara wrote:
> >>    
> >>
> >>>Hi,
> >>>
> >>>Maybe someone can suggest how to bypass this problem.
> >>>
> >>>Background:
> >>>I took a copy of asterisk from CVS and did the 'make clean ; make 
> >>>install ; make samples' and tried starting it (with all the configs 
> >>>unchanged) just to see if it would start.
> >>>
> >>>Nope - instant Segmentation Fault.
> >>>
> >>>So - after a bit of tracking around with 'ddd' I found that the problem 
> >>>is in the 'monitor' thread of the 'chan_vpb' driver.
> >>>
> >>>The SEGV occurs on line 142 of 'vpb-driver-2.2.34/src/fifo.cpp' - not 
> >>>surprising since it is handed a NULL pointer as it's queue to read from.
> >>>This was called from line 2185 of 'vpb-driver-2.2.34/src//vpbapi.cpp' 
> >>>and is where the 'vpb_get_event_sync' routine tries to do an initial 
> >>>read from a queue pointer (variable name is APIQ) ... and this pointer 
> >>>is also NULL.
> >>>
> >>>Since I dont have a Voicetronix Voice Processing Board (VPB) in the 
> >>>system, it's not surprising that all the setup stuff is null or not 
> >>>initialised.
> >>>
> >>>My question is:  How do I tell the configs that I dont have a VPB 
> >>>installed? - as a secondary issue, somewhere in the startup, the 
> >>>initialisation of the VPB card should have failed and not let this 
> >>>situation move forward to where it SEGV's .... if there is no config 
> >>>file change I can make, can someone point me to (roughly) where the 
> >>>initialisation happens so that I can make it tolerate the lack of hardware.
> >>>
> >>>Regards
> >>>Ron O'Hara
> >>>
> >>>
> >>>_______________________________________________
> >>>Asterisk-Dev mailing list
> >>>Asterisk-Dev at lists.digium.com
> >>>http://lists.digium.com/mailman/listinfo/asterisk-dev
> >>>      
> >>>
> 
> 
> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
-- 
Steven Critchfield  <critch at basesys.com>