ID:               21478
 Updated by:       [EMAIL PROTECTED]
 Reported By:      [EMAIL PROTECTED]
 Status:           Verified
 Bug Type:         Scripting Engine problem
 Operating System: linux
 PHP Version:      4CVS-2003-01-06 (dev)
 New Comment:

sniper: i tried the latest stable snapshot (php4-STABLE-200303200830)
and i couldnt reproduce the bug anymore..

but then, if its as elusive as polita said in #2 any changes to the
code might have made it dissapear (had lots of them in the last 2
days)..

I also tried php4-200303182230 to confirm that that might not be the
case, but it has gone away also... if i spot any more segfaults ill do
the wise thing and archive the scripts / database, if it can be
reproduced ;)


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

[2003-03-19 15:53:36] [EMAIL PROTECTED]

I don't know what this 4.5-dev is..since the only official
development branches are PHP_4_3 and the php5 module.

Try this snapshot:
http://snaps.php.net/php4-STABLE-200303192030.tar.gz

If that doesn't work, but the RC1 works, then it's a problem with the
build tools on the snaps.php.net machine.

(Please send me that test script you used when testing 4.3.2-RC1)






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

[2003-03-19 15:18:36] [EMAIL PROTECTED]

sniper, yes, i wasn't able to reproduce it on php4.3.2rc1

i did have one segfault it normal operation mode (not inside gdb), but
i couldnt reproduce it in any way or form similar to the process of
reproducing on the latest -STABLE or 4.5-dev snapshots

as far as i can tell 4.3-dev and 4.5-dev are subject to this.. im not
even going to guess what goes on in 5.0-dev yet..

btw, there is a slight difference between the backtrace ilia got above
and mine, so it might be an unrelated problem... still the same scope
and behaviour thou.

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

[2003-03-18 20:08:32] [EMAIL PROTECTED]

[To: [EMAIL PROTECTED] 
Did I understand correctly that you can't reproduce this
with 4.3.2RC1, but you CAN reproduce it with the latest
stable snapshot?? 

This might mean that some tools on the machine generating
the snapshots are bad versions..
(the RC1 source package was generated on my machine :)


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

[2003-03-18 13:45:09] [EMAIL PROTECTED]

ok, i cant reproduce the behaviour on my part on as low as php-4.3.2RC1
(this one works flawlessly, as far as i can tell).

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

[2003-03-18 12:42:44] [EMAIL PROTECTED]

seems to be identical on the last 4.3-STABLE snapshot from ~20 minutes
ago, i guess its the same on 4.5

i will try to track down the 4.3.1 source version and try if it crashes
there too, i kinda hope it doesn't.

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

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/21478

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

Reply via email to