Edit report at https://bugs.php.net/bug.php?id=62929&edit=1

 ID:                 62929
 Comment by:         sergiu dot ionescu at gmail dot com
 Reported by:        sergiu dot ionescu at gmail dot com
 Summary:            Segmentation fault on Zend Framework application
 Status:             Open
 Type:               Bug
 Package:            *General Issues
 Operating System:   Ubuntu 10.04.4 LTS
 PHP Version:        PHP 5.3.16
 Block user comment: N
 Private report:     N

 New Comment:

Setting apc.enable_cli=0 so far has eliminated the issue.

I don't this fixed the underlying issue but at least it gets rid of the nasty 
exit code at the end on the script.


Previous Comments:
------------------------------------------------------------------------
[2012-08-28 08:04:19] larue...@php.net

if I don't get a script to reproduce it, then I think,, I can do nothing.. 
since 
there is not much info can get from the backtrace

------------------------------------------------------------------------
[2012-08-28 07:02:45] sergiu dot ionescu at gmail dot com

I could, but i think it won't help much. As i stated initially it's a cli 
script form a Magento/ZF application with quite a few contributed modules.

If i can get to a one file script that produces the error i will post it.
Is there anything else you can do while you don't have that?

------------------------------------------------------------------------
[2012-08-28 02:47:44] larue...@php.net

could you give us a reproducable script, or scripts?  thanks, :)

------------------------------------------------------------------------
[2012-08-27 16:15:38] sergiu dot ionescu at gmail dot com

After updating all the extensions i still get the same thing.

I extra detail i can provide is that i occasionally get 
zend_mm_heap corrupted
instead of segmentation fault

and the line where the segfault occurs is the condition line from:

#if ZEND_MM_SAFE_UNLINKING
                if (UNEXPECTED(prev->next_free_block != mm_block) || 
UNEXPECTED(next->prev_free_block != mm_block)) {
                        zend_mm_panic("zend_mm_heap corrupted");
                }
#endif

------------------------------------------------------------------------
[2012-08-27 14:55:12] sergiu dot ionescu at gmail dot com

Hello,
I have compiled PHP 5.3.16(http://kr.php.net/get/php-5.3.16.tar.bz2) and i am 
experiencing similar issues.

The new back-trace is:

[Thread debugging using libthread_db enabled]

Program received signal SIGSEGV, Segmentation fault.
0x000000000068a7fb in zend_mm_remove_from_free_list (heap=0xe73290, 
mm_block=0x2ee4168) at /home/vagrant/php-5.3.16/Zend/zend_alloc.c:845
845                     if (UNEXPECTED(prev->next_free_block != mm_block) || 
UNEXPECTED(next->prev_free_block != mm_block)) {
(gdb) bt
#0  0x000000000068a7fb in zend_mm_remove_from_free_list (heap=0xe73290, 
mm_block=0x2ee4168) at /home/vagrant/php-5.3.16/Zend/zend_alloc.c:845
#1  0x000000000068a9ab in _zend_mm_free_int (heap=0xe73290, p=0x2ee4128) at 
/home/vagrant/php-5.3.16/Zend/zend_alloc.c:2029
#2  0x000000000069fcd0 in destroy_zend_class (pce=<value optimized out>) at 
/home/vagrant/php-5.3.16/Zend/zend_opcode.c:187
#3  0x00000000006b43d5 in zend_hash_apply_deleter (ht=0xe73be0, p=0x142dda0) at 
/home/vagrant/php-5.3.16/Zend/zend_hash.c:612
#4  0x00000000006b44e9 in zend_hash_reverse_apply (ht=0xe73be0, 
apply_func=0x69aed0 <clean_non_persistent_class>) at 
/home/vagrant/php-5.3.16/Zend/zend_hash.c:762
#5  0x000000000069bbbe in shutdown_executor () at 
/home/vagrant/php-5.3.16/Zend/zend_execute_API.c:312
#6  0x00000000006a85c2 in zend_deactivate () at 
/home/vagrant/php-5.3.16/Zend/zend.c:891
#7  0x0000000000654305 in php_request_shutdown (dummy=<value optimized out>) at 
/home/vagrant/php-5.3.16/main/main.c:1661
#8  0x0000000000733dfa in main (argc=<value optimized out>, argv=<value 
optimized out>) at /home/vagrant/php-5.3.16/sapi/cli/php_cli.c:1368

I am still using some on the old php5.3.2 extensions but i am upgrading the one 
by one - just in case i catch the culprit.

Please let me know if i can provide additional details.

Thanks.

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


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

    https://bugs.php.net/bug.php?id=62929


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

Reply via email to