ID: 28706 Updated by: [EMAIL PROTECTED] Reported By: LarryJAdams at comcast dot net -Status: Feedback +Status: No Feedback Bug Type: Program Execution Operating System: Windows2000/XP PHP Version: 4.3.7 New Comment:
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". Previous Comments: ------------------------------------------------------------------------ [2004-06-09 09:42:10] [EMAIL PROTECTED] 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. There is no way we can fix this with this little information. ------------------------------------------------------------------------ [2004-06-09 06:23:21] LarryJAdams at comcast dot net Description: ------------ I am modifying an application in Ansi C that calls PHP.EXE utilizing the POPEN command. The C program is utilizing threads and issuing a thread lock prior to calling, but it appears that the PHP program is stepping on some of the memory used by the C program causing an eventual lockup of the application. This has been noted by some of the memory and variables displayed in debug mode that have PHP artifacts in them. This same program calls PHP within unix without issue. Reproduce code: --------------- This is quite involved. You need the entire application. Expected result: ---------------- Normal termination of PHP without interfering with the other application. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=28706&edit=1
