ID: 26666 Updated by: [EMAIL PROTECTED] Reported By: jan at horde dot org -Status: Open +Status: Feedback Bug Type: Zend Engine 2 problem Operating System: Linux PHP Version: 5CVS-2003-12-19 (dev) New Comment:
Fatal error: main(): Failed opening required 'Horde/MIME/MIME.php' (include_path='/home/jani/prop_test/libs/') in /home/jani/prop_test/libs/Horde/MIME/Part.php on line 3 Are you sure you can't include more files in there? Previous Comments: ------------------------------------------------------------------------ [2004-01-16 12:55:47] jan at horde dot org I hope this link doesn't wrap: http://cvs.horde.org/co.php/framework/MIME/MIME/Part.php?sa=1&r=1.159&p=1 ------------------------------------------------------------------------ [2004-01-16 12:54:20] jan at horde dot org Oops, sorry. Damn include_path! ;-) http://cvsweb.horde.org/co.php/framework/MIME/MIME/Part.php?sa=1&r=1.159&p=1 Sorry about the big scripts, but whenever I tried to strip it down, the crash went away. ------------------------------------------------------------------------ [2004-01-16 11:12:08] [EMAIL PROTECTED] The provided test package is not complete..it misses at least Horde/MIME/Part.php (you really ought to cut down the stuff a lot :) ------------------------------------------------------------------------ [2003-12-31 08:15:03] jan at horde dot org I managed to create a medium sized test case, unfortunately the bug disappeared as soon as I tried to strip it further down. Get www.horde.org/~jan/prop_test.tar.gz, unpack it and run ob_vars.php with a current HEAD cli. It segfaults with the last statement, but this seems to only a followup bug. If you look at the test script, the output and the MIME_Message::buildMessage() method, you will easily see wha t is going wrong. The strange thing is that in production, these UNKNOWN:0 properties happen to only two properties of the object, always the same two and no obvious pattern that I see for those. ------------------------------------------------------------------------ [2003-12-21 08:01:43] jan at horde dot org This is the output from valgrind: VG_(get_memory_from_mmap): newSuperblock's request for 1515872256 bytes failed. VG_(get_memory_from_mmap): 102113062 bytes already allocated. No wonder that it crashes. The question is, why does this only happen in HEAD and why does the memory_limit doesn't prevent this. I can't really say when this started because I don't use PHP5 regularly. But it definitely *did* happen before the recent crash bugs/fixes. ------------------------------------------------------------------------ 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/26666 -- Edit this bug report at http://bugs.php.net/?id=26666&edit=1
