← Back to team overview

ius-coredev team mailing list archive

Re: [Question #224628]: Segfault with PDFlib

 

Question #224628 on IUS Community Project changed:
https://answers.launchpad.net/ius/+question/224628

Marcel Lindenbergh gave more information on the question:
Jusr ran Valgrind on the test script and here is it's output:

==3513== Memcheck, a memory error detector
==3513== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==3513== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
==3513== Command: php pdflib_core_dump.php
==3513== 
==3513== Invalid read of size 8
==3513==    at 0x5EC697: zend_hash_destroy (in /usr/bin/php)
==3513==    by 0xED6D749: ??? (in /usr/lib64/php/modules/libpdf_php.so)
==3513==    by 0x606F6B: zend_objects_store_del_ref_by_handle_ex (in /usr/bin/php)
==3513==    by 0x606F92: zend_objects_store_del_ref (in /usr/bin/php)
==3513==    by 0x5D1D29: _zval_ptr_dtor (in /usr/bin/php)
==3513==    by 0x5EC364: ??? (in /usr/bin/php)
==3513==    by 0x5EC468: zend_hash_reverse_apply (in /usr/bin/php)
==3513==    by 0x5D31D4: ??? (in /usr/bin/php)
==3513==    by 0x5DFE93: ??? (in /usr/bin/php)
==3513==    by 0x5825E4: php_request_shutdown (in /usr/bin/php)
==3513==    by 0x688FEE: ??? (in /usr/bin/php)
==3513==    by 0x68A3B7: ??? (in /usr/bin/php)
==3513==  Address 0x20 is not stack'd, malloc'd or (recently) free'd
==3513== 
==3513== 
==3513== Process terminating with default action of signal 11 (SIGSEGV)
==3513==  Access not within mapped region at address 0x20
==3513==    at 0x5EC697: zend_hash_destroy (in /usr/bin/php)
==3513==    by 0xED6D749: ??? (in /usr/lib64/php/modules/libpdf_php.so)
==3513==    by 0x606F6B: zend_objects_store_del_ref_by_handle_ex (in /usr/bin/php)
==3513==    by 0x606F92: zend_objects_store_del_ref (in /usr/bin/php)
==3513==    by 0x5D1D29: _zval_ptr_dtor (in /usr/bin/php)
==3513==    by 0x5EC364: ??? (in /usr/bin/php)
==3513==    by 0x5EC468: zend_hash_reverse_apply (in /usr/bin/php)
==3513==    by 0x5D31D4: ??? (in /usr/bin/php)
==3513==    by 0x5DFE93: ??? (in /usr/bin/php)
==3513==    by 0x5825E4: php_request_shutdown (in /usr/bin/php)
==3513==    by 0x688FEE: ??? (in /usr/bin/php)
==3513==    by 0x68A3B7: ??? (in /usr/bin/php)
==3513==  If you believe this happened as a result of a stack
==3513==  overflow in your program's main thread (unlikely but
==3513==  possible), you can try to increase the size of the
==3513==  main thread stack using the --main-stacksize= flag.
==3513==  The main thread stack size used in this run was 10485760.
==3513== 
==3513== HEAP SUMMARY:
==3513==     in use at exit: 4,107,951 bytes in 20,625 blocks
==3513==   total heap usage: 22,218 allocs, 1,593 frees, 4,322,771 bytes allocated
==3513== 
==3513== LEAK SUMMARY:
==3513==    definitely lost: 0 bytes in 0 blocks
==3513==    indirectly lost: 0 bytes in 0 blocks
==3513==      possibly lost: 0 bytes in 0 blocks
==3513==    still reachable: 4,107,951 bytes in 20,625 blocks
==3513==         suppressed: 0 bytes in 0 blocks
==3513== Rerun with --leak-check=full to see details of leaked memory
==3513== 
==3513== For counts of detected and suppressed errors, rerun with: -v
==3513== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 142 from 9)
Segmentation fault (core dumped)

-- 
You received this question notification because you are a member of IUS
Core Development, which is an answer contact for IUS Community Project.