I also suspect that the changes (in the version branching) are causing the
strange errors.
The last version of PHP 4.0.6-dev works fine with adodb and the MSXML Parser
3.0 with both isapi and cgi.

-----Original Message-----
From: Bug Database [mailto:[EMAIL PROTECTED]]
Sent: Saturday, 19 May 2001 11:04 PM
Subject: Bug #10580 Updated: Access Violation using ADODB

ID: 10580
Updated by: phanto
Status: Open
Bug Type: COM related
Operating system:
PHP Version: 4.0.7-dev (dated 18-May-2001)
Assigned To:

hmm, i haven't changed anything since the 15.3.2001. but afaik there where
changes in the zend-api after branching 4.0.6. maybe they are causing these
errors with isapi. do you have any problems with adodb and the cgi version ?
the problem with the XML Parser is known (#10851), but at the moment i don't
know the reason. maybe someone could help investigating .. ;)

Previous Comments:

[2001-05-18 22:45:44] [EMAIL PROTECTED]
Hi,  The current version (18-May) could not load in Windows at all, so I
cannot test that version. Curiously, the version number of PHP is 4.0.7-dev.
Testing the last version (17-May), I found that the error is generated when
it executes this line of code:  for ($rowcount = 0; !$rs->EOF;
++$rowcount, $rs->MoveNext()) {    // some code  }  Specifically, it is the
condition ( $rs->EOF ) that causes the Access Violation. All else works ok.
$rs->EOF should return a boolean datatype.  MSXMLParser also still causes
Access Violation when calling loadXML($xmldata)  When running PHP as CGI
(for the MSXMLParser script), I get this Application Error message: "The
instruction at "0x1008d824" referenced memory at "0x3c0a3e64". The memory
could not be "written"."  The last version that worked with COM was PHP
4.0.6-dev, before it turned 4.0.7-dev.


[2001-05-18 11:24:23] [EMAIL PROTECTED]
is it ? i was able to run your ado script successfully. are you using the
isapi or the cgi version of php. isapi isn't stable yet.  -harald


[2001-05-16 08:42:01] [EMAIL PROTECTED]
COM broken in PHP version 4.0.7-dev


[2001-05-16 08:34:57] [EMAIL PROTECTED]
Bug reopened, CVS dated 16 May 2001,  message when accessing database: PHP
has encountered an Access Violation at 011CD614


[2001-05-08 20:12:03] [EMAIL PROTECTED]
works here.  the only mistake i found was, that if either the connect string
or the query was wrong $conn->execute() returned a nullpointer instead of a
valid recordset. this only produced a warning so there was a nullpointer
exception at the first attempt to access $rs->... now i produce an error
(unfortunatelly this causes the script to stop). i'll fix this in the code
and switch back to a warning, but i think it's ok for now.


The remainder of the comments for this report are too long.  To view the
rest of the comments, please view the bug report online.

ATTENTION! Do NOT reply to this email!
To reply, use the web interface found at

PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to