[asterisk-dev] Re: agi segfaults 1.2.9.1

Kevin P. Fleming kpfleming at digium.com
Wed Jun 14 06:37:13 MST 2006


----- Julian Lyndon-Smith <asterisk at dotr.com> wrote:
> I'm sure that part of Kevin's email was cut off, and that he meant to
> 
> say in addition was "and we'd like to be made aware of them so that
> they 
> can be fixed in order to make asterisk an even more reliable system"

No, it was not. It is not possible to completely validate every set of parameters sent to every single application/function/AGI command/etc. in Asterisk. Even if it was possible, it's not worth the effort or the time/memory/etc. cost it would put on the users of Asterisk.

> having reported bug #7354 earlier today, a crash when invalid
> parameters 
> are passed to AddQueueMember

Invalid parameters are one thing, no parameter at all (when one is clearly documented to be required) is something else entirely. With that said, no matter how much you want to try, there is no amount of code we can put into things like AddQueueMember that will always guarantee that nothing bad will happen if you specify invalid parameters.

-- 
Kevin P. Fleming
Senior Software Engineer
Digium, Inc.




More information about the asterisk-dev mailing list