Error or Warnings in script, that use ob_start("callback") or ob_get_contents() can cause buffer to be "cut off"  or completly crippled and filled with trash ....

ob_start("callback_func")
{
// main loop
do something here  

output something here
}

function callback_func($buffer)
	{
$result=do_something( $buffer);
return $result;
}


if some error or waring occures in  main loop, content of the output buffer may be 
crippled, seems that ob_get_content() returns some short snipplet of  binary data  only , in my case it is    ???U?1???t??B????????u?U???e?[^_]?W?j  or shortened ( not all length  of the output buffer  is parsed to callback_func).




I have sugestion, how PHP should treat errors in the output_buffered scripts.
If error occures in the main loop (not in the callback function) ,all output of the script with  error or waring messages appended  SHOULD be passed as parameter to callback_function...

If error occures inside the callback_function, SHOULD BE at least error message  send to browser.