[asterisk-dev] Re: agi segfaults 1.2.9.1

[Kevin P. Fleming]

----- Samuel Tardieu <sam at rfc1149.net> wrote:
> I'm not sure I understand your answer. Do you mean that it is
> acceptable to have the whole PBX *crash* in some situations?

Thanks for putting words in my mouth (message).

If you are writing an AGI and connecting it to your Asterisk PBX, and you clearly do something wrong like 'EXEC BACKGROUND' without specifying a file to play (when clearly 'EXEC BACKGROUND' _requires_ the name of a file to play), then yes, you can expect Asterisk to do bad things, including crash.

If you are allowing your end users to connect to Asterisk in such a way that they can cause this behavior, then you should not be doing that. If this was happening when something was sent via SIP, IAX2 or some other 'end user' interface, then we would immediately fix it.

If you think it's possible to write Asterisk in such a way as to guarantee that it will NEVER crash when given bad input via it's programmer interfaces, then feel free to supply the hundreds of thousands of lines of code that it will require to get there (and by the way, all that input sanity checking will drastically reduce performance for the 99.9999% of the time that the input is perfectly fine as well).

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