php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #31840 COM extensibility appears to hinder code execution
Submitted: 2005-02-04 09:04 UTC Modified: 2005-02-21 19:55 UTC
Votes:1
Avg. Score:3.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:1 (100.0%)
Same OS:0 (0.0%)
From: stefan dot mueller at issp dot cc Assigned:
Status: No Feedback Package: COM related
PHP Version: 4.3.10 OS: Windows 2000 Server/SP4
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please — but make sure to vote on the bug!
Your email address:
MUST BE VALID
Solve the problem:
2 + 33 = ?
Subscribe to this entry?

 
 [2005-02-04 09:04 UTC] stefan dot mueller at issp dot cc
Description:
------------
When instantiating a new COM object PHP produces no output. Reproduce code given. PHP running with binaries from binary distributions available on www.php.net; No extensions activated.

Reproduce code:
---------------
<?
	echo "init phase\r\n";

        $rst = new COM("ADODB.Recordset") or die("fail");

        $rst->Open("SELECT * FROM sysdatabases",
                "Data Source=localhost;User Id=sa;Password=sa;" .
                "Provider=SQLOLEDB.1;Initial Catalog=master");
                   

        echo "got my rst successfully";
?>


Expected result:
----------------
Version 4.3.8 placed in the same directory (C:\php\php.exe) wrote this to the stdout when passing the file to the interpreter via command line prompt. This is the behaviour I do expect the interpreter to write to stdout.

<snip>
Content-type: text/html
X-Powered-By: PHP/4.3.8

init phase
got my rst successfully
</snap>

Actual result:
--------------
No output to stdout with 4.3.10. I tried the following:

+ moving php.ini from windir to desktop temporarily
+ replace existing php.ini with php.ini-recommended from 4.3.10 and reconfigure it
+ explicitly enabling the display of errors (display_errors, display_startup_errors) through the INI file
+ execute script on Apache2 (configured with the experimental server module) and check Apaches' error log. --> no new entries after scripts' execution.


Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2005-02-21 19:55 UTC] sniper@php.net
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.


 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Thu Apr 25 12:01:31 2024 UTC