Bug #16038 Updated: COM Object: Works fine with PHP 4.0.6, causes Access Violation with 4.1.1
| From: | phanto@php.net | Date: | Fri, 15 Mar 2002 17:35:16 +0000 |
| Subject: | Bug #16038 Updated: COM Object: Works fine with PHP 4.0.6, causes Access Violation with 4.1.1 | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-2596@lists.php.net to get a copy of this message | ||
ID: 16038
Updated by: phanto@php.net
Reported By: lightwing@bluewin.ch
-Status: Open
+Status: Closed
Bug Type: COM related
Operating System: Windows NT 4.0 Server
PHP Version: 4.1.1
New Comment:
this sometimes happens to me when i have a corrupt build. download your
copy from another source and try it again.
Previous Comments:
------------------------------------------------------------------------
[2002-03-13 06:35:34] lightwing@bluewin.ch
I wrote a very simple ActiveX Library with Delphi 5, containing an
Automation Object with just a few functions. Calling this object from
Delphi, ASP or PHP 4.0.6 worked fine, but from PHP 4.1.1 did not.
$myObj = new COM(...); or $myObj = com_load(...); worked and returned
an object (at least echo $myObj; said so) and $myObj = null destroyed
it, but whenever I called any object function (whether by $myObj->...;
or com_invoke(...) did not matter), I got an Access Violation.
I tried lots of different versions with functions actually doing
nothing at all and with different kinds of parameters or none, the
result was always the same. Also, the problem occurred on both Apache
and IIS, and with the Library written under Delphi as well as under
Visual C++.
Only when replacing PHP 4.1.1 by older 4.0.6 (I did not replace
php.ini), it suddenly worked as expected.
Personally, I am satisfied now. But for others who might spend a lot of
time and nerves as I did, i thought it worth dropping this note
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=16038&edit=1