Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 0.3.3

Bug #21113 %Angosso!!!%
Submitted: 2016-09-09 12:44 UTC
From: mbiama Assigned:
Status: Open Package: URI_Template (version 0.3.3)
PHP Version: 5.6.25 OS: /proc/sys/kernel/core_pattern
Roadmaps: (Not assigned)    
Subscription  


 [2016-09-09 12:44 UTC] mbiama (Roger Mbiama)
Description: ------------ make sure the directory is writable by PHP Set the ulimit (see above how to do it). Restart/rerun PHP. After that any process crashing in my system, including PHP, will leave its core file in the directory you've specified in core_pattern. Test script: --------------- Once you have the core file: Run gdb with the path to the PHP or PHP-enabled httpd binary, and path to the core file. Some examples: gdb /var/www/vhosts/angosso.net/apache/sbin/httpd /var/www/vhosts/angosso.net/apache/sbin/core gdb /home/angosso.net/dev/php-snaps/sapi/cli/php /home/angosso.net/dev/testing/core At the gdb prompt, run: (gdb) bt If you can't get a core file: Run httpd -X under gdb with something like: gdb /var/www/vhosts/angosso.net/apache/sbin/httpd (gdb) run -X Then use your web browser and access your server to force the crash. You should see a gdb prompt appear and some message indicating that there was a crash. At this gdb prompt, type: (gdb) bt or, running from the commandline gdb /home/angosso.net/dev/php-snaps/sapi/cli/php (gdb) run /var/www/vhosts/angosso.net/httpdocs/script.php (gdb) bt This should generate a backtrace, that you should submit in the bug report, along with any other details you can give us about your setup, and offending script. Locating which function call caused a segfault: You can locate the function call that caused a segfault, easily, with gdb. First, you need a core file or to generate a segfault under gdb as described above. In PHP, each function is executed by an internal function called execute() and has its own stack. Each line generated by the bt command represents a function call stack. Typically, you will see several execute() lines when you issue bt. You are interested in the last execute() stack (i.e. smallest frame number). You can move the current working stack with the up, down or frame commands. Below is an example gdb session that can be used as a guideline on how to handle your segfault. Sample gdb session (gdb) bt #0 0x080ca21b in _efree (ptr=0xbfffdb9b) at zend_alloc.c:240 #1 0x080d691a in _zval_dtor (zvalue=0x8186b94) at zend_variables.c:44 #2 0x080cfab3 in _zval_ptr_dtor (zval_ptr=0xbfffdbfc) at zend_execute_API.c:274 #3 0x080f1cc4 in execute (op_array=0x816c670) at ./zend_execute.c:1605 #4 0x080f1e06 in execute (op_array=0x816c530) at ./zend_execute.c:1638 #5 0x080f1e06 in execute (op_array=0x816c278) at ./zend_execute.c:1638 #6 0x080f1e06 in execute (op_array=0x8166eec) at ./zend_execute.c:1638 #7 0x080d7b93 in zend_execute_scripts (type=8, retval=0x0, file_count=3) at zend.c:810 #8 0x0805ea75 in php_execute_script (primary_file=0xbffff650) at main.c:1310 #9 0x0805cdb3 in main (argc=2, argv=0xbffff6fc) at cgi_main.c:753 #10 0x400c91be in __libc_start_main (main=0x805c580 , argc=2, ubp_av=0xbffff6fc, init=0x805b080 <_init>, fini=0x80f67b4 <_fini>, rtld_fini=0x4000ddd0 <_dl_fini>, stack_end=0xbffff6ec) at ../sysdeps/generic/libc-start.c:129 (gdb) frame 3 #3 0x080f1cc4 in execute (op_array=0x816c670) at ./zend_execute.c:1605 (gdb) print (char *)(executor_globals.function_state_ptr->function)->common.function_name $14 = 0x80fa6fa "pg_result_error" (gdb) print (char *)executor_globals.active_op_array->function_name $15 = 0x816cfc4 "result_error" (gdb) print (char *)executor_globals.active_op_array->filename $16 = 0x816afbc "/home/var/www/vhosts/angosso.net/php/DEV/angosso.php" (gdb)

Comments

 [2016-09-09 12:48 UTC] mbiama (Roger Mbiama)