#18186 [Opn->Fbk]: warning using PEAR::isError

From: Date: Fri, 02 Aug 2002 20:50:41 +0000
Subject: #18186 [Opn->Fbk]: warning using PEAR::isError
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-15863@lists.php.net to get a copy of this message
ID: 18186 Updated by: iliaa@php.net Reported By: stevem@solveinteractive.com -Status: Open +Status: Feedback Bug Type: Class/Object related Operating System: Unix PHP Version: 4.2.1 New Comment: I've tried to replicate the bug using latest CVS, but I cannot, please try the latest CVS and see if the problem still happens. Previous Comments: ------------------------------------------------------------------------ [2002-07-08 10:15:23] stevem@solveinteractive.com The error is 100% reproducable. I am unable to test with the latest version of the CVS. If there is something else I could try, please let me know. Thank you for your assistance. ------------------------------------------------------------------------ [2002-07-06 09:10:28] jan@php.net apologies ;) ------------------------------------------------------------------------ [2002-07-06 08:54:51] sander@php.net Not so fast, Jan... this is an error generated by PHP (well, Zend to be precise, zend_execute.c). This should never happen. Status -> feedback. ------------------------------------------------------------------------ [2002-07-06 08:51:10] jan@php.net Sorry, but the bug system is not the appropriate forum for asking support questions. Your problem does not imply a bug in PHP itself. For a list of more appropriate places to ask for help using PHP, please visit http://www.php.net/support.php Thank you for your interest in PHP. is there a server running on \'localhost\' port 8090? ------------------------------------------------------------------------ [2002-07-06 05:32:54] sander@php.net Can't reproduce with latest CVS. Is this error 100% reproducable for you? Can you try the latest CVS and see if the error still persists? ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/18186 -- Edit this bug report at http://bugs.php.net/?id=18186&edit=1

« previous php.bugs (#15863) next »