ID: 44546 Updated by: [EMAIL PROTECTED] Reported By: l dot alberton at quipo dot it -Status: Bogus +Status: Assigned Bug Type: SPL related Operating System: Windows PHP Version: 5.3CVS-2008-03-27 (snap) -Assigned To: +Assigned To: dmitry
Previous Comments: ------------------------------------------------------------------------ [2008-04-02 09:40:36] [EMAIL PROTECTED] Same as bug #44226 ------------------------------------------------------------------------ [2008-03-29 06:25:34] l dot alberton at quipo dot it It might be the case that the bug isn't in SplHeap::next() after all, that's just the way I experienced it. This might be a dupe of http://bugs.php.net/bug.php?id=44226 ------------------------------------------------------------------------ [2008-03-28 16:06:29] [EMAIL PROTECTED] Your build/snapshot appears to be broken, I can't find anyone except you that can reproduce it under windows. Please try to run the complete test suite so you can see whether you find other crashes.... ------------------------------------------------------------------------ [2008-03-28 11:30:44] l dot alberton at quipo dot it I think I have a better reproducing script: ================================= $pqueue = new SplPriorityQueue(); $pqueue->insert('a', 1); $pqueue->insert('b', 2); try { echo $pqueue->extract(); echo $pqueue->extract(); echo $pqueue->extract(); } catch (RuntimeException $e) { echo "\nERROR: ".$e->getMessage(); } ================================= Here, I insert 2 elements in the queue, and try to extract 3 elements. The last extract() call should trigger a RuntimeException, and this is the case when running the script from the command line. When running it in a web browser, Apache crashes. HTH ------------------------------------------------------------------------ [2008-03-27 18:47:28] l dot alberton at quipo dot it I have no idea. Nevertheless, that's the way I experienced the crash, and without calling next() everything was fine. ------------------------------------------------------------------------ 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/44546 -- Edit this bug report at http://bugs.php.net/?id=44546&edit=1
