Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:18632 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 5702 invoked by uid 1010); 1 Sep 2005 00:30:36 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 5687 invoked from network); 1 Sep 2005 00:30:36 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Sep 2005 00:30:36 -0000 X-Host-Fingerprint: 64.233.184.205 wproxy.gmail.com Linux 2.4/2.6 Received: from ([64.233.184.205:9674] helo=wproxy.gmail.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id D2/74-15098-CAB46134 for ; Wed, 31 Aug 2005 20:30:36 -0400 Received: by wproxy.gmail.com with SMTP id i22so61346wra for ; Wed, 31 Aug 2005 17:30:32 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=YBG+ioFRmVqqA9J0GuppXOX26NJrS/ASwPxJxY4EjqyH17cY0skp+OWPJSG3l00yVfEoyDANHmPy0Fq0GmQ/t7yA4Q6Zn+hU/mte9wb62tncHTqLuWiQ9PUmVDdIQIat3X6B0vMB36q+MG5pNVv5vch4bsPfdGBh4oZSJ9CJiWA= Received: by 10.54.52.63 with SMTP id z63mr756533wrz; Wed, 31 Aug 2005 17:30:32 -0700 (PDT) Received: by 10.54.107.8 with HTTP; Wed, 31 Aug 2005 17:30:32 -0700 (PDT) Message-ID: <57792e8505083117305fe772b9@mail.gmail.com> Date: Wed, 31 Aug 2005 17:30:32 -0700 To: internals Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Bugs in 5.0.5 and 5.1 RCs From: iamstever@gmail.com (steve) OK, knowing *exactly* what is going on when there are lots of other peoples code involved (a framework, ADODB, JPSpan, etc.) is tuff, but here is what I think: The lowdown: mysqli seems to be gone by the time the shutdown function is called (the error being "Couldn't fetch mysqli"). That makes an exception, and depending on whatever else is loaded, it will either try to squelch the error or throw a new exception which leads to the error at Unknown at line 0 bug. At any rate, there are two problems: 1) That the newly thrown exception blows up into a fatal error that doesn't list the file or line number. 2) mysqli is unloaded(!?) (or appears to be) before the the user's shutdown function is called. This one is SERIOUS -- I use it to save session data, etc. This then becomes impossible to do. In the backtrace you'll notice that the function table (in fact, all parameters, are, as Markus says, borked!) when going from call_user_function() to call_user_function_ex() on the mysqli extention. #24 0x0823e95c in call_user_function_ex (function_table=3D0x1, object_pp=3D0x1, function_name=3D0x1, retval_ptr_ptr=3D0x1, param_count=3D1= , params=3D0x1, no_separation=3D1, symbol_table=3D0x1) at /php-5.1.0RC1/Zend/zend_execute_API.c:571 #25 0x0823e998 in call_user_function (function_table=3D0xa0a2350, object_pp=3D0x0, function_name=3D0xa43f80c, retval_ptr=3D0xbfe96ad0, param_count=3D0, params=3D0xa448280) at /php-5.1.0RC1/Zend/zend_execute_API.c:544 I guess I should make a bug report or two. ?? -steve--