valgrind log for segfault

# cat php.log
==21792== Memcheck, a memory error detector
==21792== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==21792== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
==21792== Command: /usr/local/sbin/php-fpm -F -e
==21792== Parent PID: 3488
==21792==
==21792== Syscall param epoll_ctl(event) points to uninitialised byte(s)
==21792==    at 0x454741E: epoll_ctl (in /lib/libc-2.12.so)
==21792==    by 0x84F4628: fpm_event_queue_add (fpm_events.c:171)
==21792==    by 0x84F506C: fpm_event_add (fpm_events.c:499)
==21792==    by 0x84FFADE: fpm_stdio_parent_use_pipes (fpm_stdio.c:250)
==21792==    by 0x84EF0CB: fpm_parent_resources_use (fpm_children.c:356)
==21792==    by 0x84EF21A: fpm_children_make (fpm_children.c:419)
==21792==    by 0x84EF3F0: fpm_children_create_initial (fpm_children.c:453)
==21792==    by 0x84EE68E: fpm_run (fpm.c:101)
==21792==    by 0x84F94DF: main (fpm_main.c:1877)
==21792==  Address 0xbecd317c is on thread 1's stack
==21792==
==21792== Syscall param epoll_ctl(event) points to uninitialised byte(s)
==21792==    at 0x454741E: epoll_ctl (in /lib/libc-2.12.so)
==21792==    by 0x84F4628: fpm_event_queue_add (fpm_events.c:171)
==21792==    by 0x84F506C: fpm_event_add (fpm_events.c:499)
==21792==    by 0x84FFB23: fpm_stdio_parent_use_pipes (fpm_stdio.c:253)
==21792==    by 0x84EF0CB: fpm_parent_resources_use (fpm_children.c:356)
==21792==    by 0x84EF21A: fpm_children_make (fpm_children.c:419)
==21792==    by 0x84EF3F0: fpm_children_create_initial (fpm_children.c:453)
==21792==    by 0x84EE68E: fpm_run (fpm.c:101)
==21792==    by 0x84F94DF: main (fpm_main.c:1877)
==21792==  Address 0xbecd317c is on thread 1's stack
==21792==
==21792== Syscall param epoll_ctl(event) points to uninitialised byte(s)
==21792==    at 0x454741E: epoll_ctl (in /lib/libc-2.12.so)
==21792==    by 0x84F4628: fpm_event_queue_add (fpm_events.c:171)
==21792==    by 0x84F506C: fpm_event_add (fpm_events.c:499)
==21792==    by 0x84F4B58: fpm_event_loop (fpm_events.c:356)
==21792==    by 0x84EE6D7: fpm_run (fpm.c:115)
==21792==    by 0x84F94DF: main (fpm_main.c:1877)
==21792==  Address 0xbecd31dc is on thread 1's stack
==21792==
==21793== Invalid read of size 1
==21793==    at 0x844DDE9: _zval_dtor_func (zend_variables.c:36)
==21793==    by 0x843D676: _zval_dtor (zend_variables.h:35)
==21793==    by 0x843D723: i_zval_ptr_dtor (zend_execute.h:79)
==21793==    by 0x843E3EE: _zval_ptr_dtor (zend_execute_API.c:424)
==21793==    by 0x844E272: _zval_ptr_dtor_wrapper (zend_variables.c:188)
==21793==    by 0x845E4FA: i_zend_hash_bucket_delete (zend_hash.c:182)
==21793==    by 0x845E5C0: zend_hash_bucket_delete (zend_hash.c:192)
==21793==    by 0x845FFD2: zend_hash_graceful_reverse_destroy (zend_hash.c:613)
==21793==    by 0x843DED6: shutdown_executor (zend_execute_API.c:244)
==21793==    by 0x844FFDC: zend_deactivate (zend.c:960)
==21793==    by 0x83D2E0D: php_request_shutdown (main.c:1878)
==21793==    by 0x84F99A1: main (fpm_main.c:1992)
==21793==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==21793==
==21793==
==21793== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==21793==  Access not within mapped region at address 0x0
==21793==    at 0x844DDE9: _zval_dtor_func (zend_variables.c:36)
==21793==    by 0x843D676: _zval_dtor (zend_variables.h:35)
==21793==    by 0x843D723: i_zval_ptr_dtor (zend_execute.h:79)
==21793==    by 0x843E3EE: _zval_ptr_dtor (zend_execute_API.c:424)
==21793==    by 0x844E272: _zval_ptr_dtor_wrapper (zend_variables.c:188)
==21793==    by 0x845E4FA: i_zend_hash_bucket_delete (zend_hash.c:182)
==21793==    by 0x845E5C0: zend_hash_bucket_delete (zend_hash.c:192)
==21793==    by 0x845FFD2: zend_hash_graceful_reverse_destroy (zend_hash.c:613)
==21793==    by 0x843DED6: shutdown_executor (zend_execute_API.c:244)
==21793==    by 0x844FFDC: zend_deactivate (zend.c:960)
==21793==    by 0x83D2E0D: php_request_shutdown (main.c:1878)
==21793==    by 0x84F99A1: main (fpm_main.c:1992)
==21793==  If you believe this happened as a result of a stack
==21793==  overflow in your program's main thread (unlikely but
==21793==  possible), you can try to increase the size of the
==21793==  main thread stack using the --main-stacksize= flag.
==21793==  The main thread stack size used in this run was 10485760.
==21793==
==21793== HEAP SUMMARY:
==21793==     in use at exit: 2,142,987 bytes in 11,946 blocks
==21793==   total heap usage: 15,458 allocs, 3,512 frees, 2,351,527 bytes allocated
==21793==
==21793== LEAK SUMMARY:
==21793==    definitely lost: 108 bytes in 1 blocks
==21793==    indirectly lost: 2,147 bytes in 26 blocks
==21793==      possibly lost: 0 bytes in 0 blocks
==21793==    still reachable: 2,140,732 bytes in 11,919 blocks
==21793==         suppressed: 0 bytes in 0 blocks
==21793== Rerun with --leak-check=full to see details of leaked memory
==21793==
==21793== For counts of detected and suppressed errors, rerun with: -v
==21793== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 53 from 10)
==21793== could not unlink /tmp/vgdb-pipe-from-vgdb-to-21793-by-???-on-???
==21793== could not unlink /tmp/vgdb-pipe-to-vgdb-from-21793-by-???-on-???
==21793== could not unlink /tmp/vgdb-pipe-shared-mem-vgdb-21793-by-???-on-???
==21792==
==21792== HEAP SUMMARY:
==21792==     in use at exit: 2,400 bytes in 35 blocks
==21792==   total heap usage: 15,300 allocs, 15,265 frees, 2,221,531 bytes allocated
==21792==
==21792== LEAK SUMMARY:
==21792==    definitely lost: 120 bytes in 2 blocks
==21792==    indirectly lost: 2,158 bytes in 28 blocks
==21792==      possibly lost: 0 bytes in 0 blocks
==21792==    still reachable: 122 bytes in 5 blocks
==21792==         suppressed: 0 bytes in 0 blocks
==21792== Rerun with --leak-check=full to see details of leaked memory
==21792==
==21792== For counts of detected and suppressed errors, rerun with: -v
==21792== Use --track-origins=yes to see where uninitialised values come from
==21792== ERROR SUMMARY: 5 errors from 3 contexts (suppressed: 53 from 10)