ID:               33036
 User updated by:  sruwhof at intervisionit dot nl
 Reported By:      sruwhof at intervisionit dot nl
 Status:           Open
 Bug Type:         Reproducible crash
 Operating System: *
 PHP Version:      5.0.4
 New Comment:

Additional information:
I've got various other crashes and weird stuff happening (only when
running 5.0.4, in 4.3.11 i've got no problem). I think the problem
persist in the memory.

Those other crashes and weird stuff have a much larger code bases and i
cant get a small reproduction codebase to submit to the bug tracker.


Previous Comments:
------------------------------------------------------------------------

[2005-05-16 17:26:19] sruwhof at intervisionit dot nl

I've tried PHP Version 5.0.5-dev but the bug still isn't fixed.

------------------------------------------------------------------------

[2005-05-15 17:34:06] [EMAIL PROTECTED]

Please try using this CVS snapshot:

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



------------------------------------------------------------------------

[2005-05-15 16:06:12] sruwhof at intervisionit dot nl

Description:
------------
Apache crashes when type hints are used in a method. An important term
for this is that the result of the method is not saved. If you do save
the result in a variable, then Apache won't crash.

My config:
PHP 5.0.4 (cli) build mar 31 2005 02:45:48
Apache 2.0.54
Windows XP SP 2

PHP runs as an apache module.

Reproduce code:
---------------
<?php
# apache crashes
class a {       
    public function a (b $p) {} 
}
class b {}

new a(new b);  // result is _not_ saved in a variable
?>



<?php
# apache doesn't crash
class a {       
    public function a (b $p) {} 
}
class b {}

$a = new a(new b);  //result is saved in a variable
?>

Expected result:
----------------
Apache crashes



------------------------------------------------------------------------


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

Reply via email to