#21319 [Fbk]: the PHP Script Interpreter crashes.

2003-01-28 Thread sniper
 ID:   21319
 Updated by:   [EMAIL PROTECTED]
 Reported By:  [EMAIL PROTECTED]
 Status:   Feedback
 Bug Type: Scripting Engine problem
 Operating System: windows xp
 PHP Version:  4.3.0
 New Comment:

Okay..btw. Why did you again use that 'Add comment' link?
The URL in the email you get does not point there..?
(just curious :)

And close this if your stuff also works with the snapshot..



Previous Comments:


[2003-01-28 03:16:01] [EMAIL PROTECTED]

Alex' script does not crash with the latest snapshot,

checking my own code..



[2003-01-27 02:50:18] [EMAIL PROTECTED]

Please try using this CVS snapshot:

  http://snaps.php.net/php4-STABLE-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php4-win32-STABLE-latest.zip





[2003-01-27 02:18:59] [EMAIL PROTECTED]

in order to set the status, i seem to have to edit this...

thank you alex, this does crash php, i hope it's the same problem.



[2003-01-25 03:31:31] [EMAIL PROTECTED]

Hello, I've run into what seems to be the same problem.
I also have a way to reproduce it:
WinXP HE (NT 5.1), Apache 1.3.27, PHP 4.3.0 on CGI-FCGI

?php
error_reporting(E_ALL ^ E_WARNING);
set_time_limit(10);

for($x=1;$x1;$x++){
$f = fsockopen('127.0.0.1',$x,$errno,$errstr,1);
print Port $x: ;
print($f)?'Success!':'Failed!';
print br /;
}
?

Almost every single time it causes an HTTP 500 Error
This from the server's log:

[Sat Jan 25 01:00:23 2003] [error] [client 127.0.0.1] Premature end of
script headers: {PATH TO PHP}/php.exe
[Sat Jan 25 01:00:23 2003] [error] [client 127.0.0.1] FATAL: 
erealloc():  Unable to allocate 10 bytes


You may need to refresh that page a few times to get the Program has
crashed and needs to close/Report to MS window. When this happens, the
browser hangs until you click something on that dialog box.

btw, I've also increased the timeout to fsockopen(), while the error
still occures, it seems easier to reproduce with lower timeouts.

I have the files appcompat.txt, manifest.txt and php.exe.mdmp generated
by the error reporting app available upon request.

Could this also be related to http://bugs.php.net/bug.php?id=21262 ?

Thank you for your time.
- Alex, http://alexnow.com



[2003-01-24 01:00:02] [EMAIL PROTECTED]

No feedback was provided for this bug for over 2 weeks, 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.



The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/21319

-- 
Edit this bug report at http://bugs.php.net/?id=21319edit=1




#21319 [Fbk]: the PHP Script Interpreter crashes.

2003-01-28 Thread sniper
 ID:   21319
 Updated by:   [EMAIL PROTECTED]
 Reported By:  [EMAIL PROTECTED]
 Status:   Feedback
 Bug Type: Scripting Engine problem
 Operating System: windows xp
 PHP Version:  4.3.0
 New Comment:

You should be using ..edit=2 (the 'Edit Submission' link)

Anyway, did the snapshot fix the problem for you or not?



Previous Comments:


[2003-01-28 11:00:25] [EMAIL PROTECTED]

I've memorized the url :) (didn't look at the email) and if i'd edit
the submission the status would be set to something other than what you
recently set it to..



[2003-01-28 05:06:55] [EMAIL PROTECTED]

Okay..btw. Why did you again use that 'Add comment' link?
The URL in the email you get does not point there..?
(just curious :)

And close this if your stuff also works with the snapshot..




[2003-01-28 03:16:01] [EMAIL PROTECTED]

Alex' script does not crash with the latest snapshot,

checking my own code..



[2003-01-27 02:50:18] [EMAIL PROTECTED]

Please try using this CVS snapshot:

  http://snaps.php.net/php4-STABLE-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php4-win32-STABLE-latest.zip





[2003-01-27 02:18:59] [EMAIL PROTECTED]

in order to set the status, i seem to have to edit this...

thank you alex, this does crash php, i hope it's the same problem.



The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/21319

-- 
Edit this bug report at http://bugs.php.net/?id=21319edit=1