#28396 [Opn->Bgs]: crash when memory limit reached

ID: 28396 Updated by: iliaa@php.net Reported By: operator at infomaniak dot ch -Status: Open +Status: Bogus Bug Type: Reproducible crash Operating System: linux glibc 2.2 PHP Version: 4.3.6 New Comment: yes Previous Comments: ------------------------------------------------------------------------ [2004-05-14 17:05:32] operator at infomaniak dot ch Finaly, this won't segfault, you were right. Then, it appears that in some rare conditions, just after memory_limit reached, segfault comes. But, this may be because of any other extension. For this, could you tell how to compile seperate extensions (ala phpize etc...) with debug enabled ? with a core compiled with --enable-debug, extensions still get build without debug... ------------------------------------------------------------------------ [2004-05-14 16:41:46] operator at infomaniak dot ch Have you really tried to put this script and run it with a php_admin_value memory_limit 512000 ? ------------------------------------------------------------------------ [2004-05-14 15:33:46] iliaa@php.net No crashes here and memory analysis tools show no suspicious operations. ------------------------------------------------------------------------ [2004-05-14 14:05:59] operator at infomaniak dot ch Alright. This is not true. Memory allocation failing due to external bad behaviour must cause segfault, not because of memory_limit reached. Then, I get exactly the same result without --enable-debug . For info, crash occurs exactly when memory_limit is reached. (output just before crash: 509528 510552 511576 with a memory limit at 512000 output got without --enable-debug) ) ------------------------------------------------------------------------ [2004-05-14 13:46:19] wez@php.net This is expected behaviour; in a debug build, when memory allocation fails, we force a segfault. Don't run debug builds in production. ------------------------------------------------------------------------ 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/28396 -- Edit this bug report at http://bugs.php.net/?id=28396&edit=1