WF>> Changing emalloc to return NULLs does not modify the program
WF>> behaviour: you (probably) receive a SIGSEGV from the emalloc
WF>> caller and the execution terminate.  I can't see a big

Making such assumptions is a good way to security holes and obscure bugs.

Stanislav Malyshev, Zend Products Engineer
[EMAIL PROTECTED] +972-3-6139665 ext.115

PHP Development Mailing List <>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to