Description: ------------ PHP Warning: PEAR_ERROR_EXCEPTION is obsolete, use class PEAR_Exception for exceptions in /usr/share/php/PEAR.php on line 894 PHP Fatal error: Wrong parameters for Exception([string $exception [, long $code [, Exception $previous = NULL]]]) in /usr/share/php/PEAR.php(895) : eval()'d code on line 1

Do you have a stack trace? (Enable xdebug to get one) I'm not sure where this is coming from. There's two issues in one. I'm not even sure if this is from HTTP_Session2 code or if this is your error handler around it.

I am not able to reliably trigger this issue.

I went through and modified most of the files in the package to use raiseError() instead of 'throw', but that did not resolve the issue. I am testing another of my sites, and I consistently get a WSOD when trying to use the package. When I comment out my calls into the package, the site displays normally.

Assigning this bug to MDB2 since I can't fix it in HTTP_Session2.

The issue is the way MDB2 uses Error objects. It does not pass a "message" parameter, which PEAR's error handler is expecting.

This was happening when taking a PEAR_Error object returned by MDB2::raiseError() and passing it back to PEAR::raiseError(). When PEAR::raiseError() receives an object, it mistakenly assumes the destination/wrapper error_object's constructor has a $message parameter. MDB2_Error::__construct() does not, so the $code parameter's value was getting passed to the $mode parameter and mayhem ensued due to unexpected modes of operation. This has been fixed by adding reflection to PEAR::raiseError() in commit 6cbc32b6cf79094fb267621ed2090567eca41bd4.

(commit hash of david's commit after my re-import is 6d10feff7b97d2f6e65396f5a1fa6dab22871824) This bug cannot be fixed in 1.9.5 with reflection since that release will still be PHP4-compatible.

The best way would be to fix MDB2_Error instead of adding special handling to PEAR_Error, but that breaks BC.