Changes between Version 2 and Version 3 of HowToReportABug/GenerateBacktrace


Ignore:
Timestamp:
2007-11-28T02:14:02+01:00 (7 years ago)
Author:
moo
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • HowToReportABug/GenerateBacktrace

    v2 v3  
    55== If you don't have a core file yet ==
    66Read [http://bugs.php.net/bugs-generating-backtrace.php generating a Backtrace] on php.net.
    7   * config xcache.coredump_directory in /etc/php.ini
    8   * Ensure that the xcache.coredump_directory has write permissions for the user who's running PHP.
     7  * config xcache.coredump_directory in /etc/php.ini, For apache + mod_php, you have CoreDumpDirectory in apache.conf
     8  * Ensure that the xcache.coredump_directory has write permissions for the user who's running PHP
    99  * Remove any limits you may have on core dump size from your shell:
    1010    * tcsh: unlimit coredumpsize
     
    1515    * PHP As Apache Module: Run httpd -X, and access the script that crashes PHP
    1616== Once you have the core file ==
    17 check where the coredump is
     17First, check where the coredump is
     18====== Checking where the coredump is ======
    1819{{{
    1920#!ShellExample
     
    2324/tmp/core
    2425}}}
    25 ok, it's there
    2626
    2727 * PHP as CGI/FastCGI: Run gdb with the path to the PHP or PHP-enabled httpd binary, and path to the core file, for example:
     28====== Generating backtrace for PHP as CGI/FastCGI ======
    2829{{{
    2930#!ShellExample
     
    3637
    3738  * PHP As Webserver Module: Run gdb with the path to the PHP or PHP-enabled httpd binary, and path to the core file, for example:
     39====== Generating backtrace for PHP as As Webserver Module ======
    3840{{{
    3941#!ShellExample