php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #31410 COM Causes crash "The memory could not be "read".
Submitted: 2005-01-04 20:57 UTC Modified: 2005-01-13 01:00 UTC
Votes:2
Avg. Score:4.0 ± 1.0
Reproduced:1 of 1 (100.0%)
Same Version:1 (100.0%)
Same OS:1 (100.0%)
From: jevans at lynch dot ca Assigned:
Status: No Feedback Package: Reproducible crash
PHP Version: 4.3.10 OS: Windows 2000 IIS
Private report: No CVE-ID: None
View Add Comment Developer Edit
Have you experienced this issue?
Rate the importance of this bug to you:

 [2005-01-04 20:57 UTC] jevans at lynch dot ca 
Description:
------------
I am using a vb build COM that pushes data to another db. 

When I run this COM, PHP crashes with the following application error:
' The instruction at "0x10038b14" referenced memory at "0x00001000". The memory could not be "read". '

This COM will establish a connection to the db and reference the path ($objActLink_Notes->ACTPath) correctly (I have checked this and printed it to a log file to make sure). It will also close the path and terminate the object.

Also, when I run this code in VB, I am able to put the note without any issues. It is just when it it compiled and installed.







Reproduce code:
---------------
$ContactID = base64_decode("VThNPiEgRDJESCEh");
$NoteText = "Testing note connection";

$objActLink_Notes = new COM("ACT_MySQL_Link.Notes") or die("Unable to instantiate COM object");

$objActLink_Notes->ACTPath = realpath("act.dbf");
$objActLink_Notes->ACTPath = 'E:\act.dbf';

$objActLink_Notes->AddNote($ContactID,$NoteText); 
$objActLink_Notes = null;

Expected result:
----------------
note to be added to the db at specified contact ID

Actual result:
--------------
When I run this COM, PHP crashes with the following application error:
' The instruction at "0x10038b14" referenced memory at "0x00001000". The memory could not be "read". '

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2005-01-04 23:56 UTC] jed@php.net 
Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.php.net/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to "Open".

Thank you for your interest in PHP.


We don\'t have your COM component, and this doesn\'t really imply a bug in PHP either, it could be in your component.
 [2005-01-05 00:02 UTC] jed@php.net 
.
 [2005-01-05 09:28 UTC] wez@php.net 
A change in the Zend Engine destabilized what we call "overloaded objects" in PHP 4.3.10.  PHP 4.3.9 works, and if you're running on a private network, you're probably better-off downgrading.  PHP 4.3.11 will correct this engine problem and is due to be release in a couple of weeks.

If you're really serious about COM access, we recommend that you upgrade to PHP 5, which has much better support for COM.

If you can reproduce your problem under PHP 4.3.9, please re-open this report, and try to include as much detail as you can to help us to replicate the problem.  I have to warn you that we don't actively support COM under PHP 4 any longer, and if PHP 5 works for you, you should use that instead.
 [2005-01-13 01:00 UTC] php-bugs at lists dot php dot net 
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Tue May 07 08:01:32 2024 UTC