Changes between Version 2 and Version 3 of HowToReportABug/GenerateBacktrace

Timestamp:

11/28/2007 02:14:02 AM (5 years ago)

Author:

moo

Comment:

--

HowToReportABug/GenerateBacktrace

@@ -5 +5 @@
 == If you don't have a core file yet ==
 Read [http://bugs.php.net/bugs-generating-backtrace.php generating a Backtrace] on php.net.
-  * config xcache.coredump_directory in /etc/php.ini
-  * Ensure that the xcache.coredump_directory has write permissions for the user who's running PHP. 
+  * config xcache.coredump_directory in /etc/php.ini, For apache + mod_php, you have CoreDumpDirectory in apache.conf
+  * Ensure that the xcache.coredump_directory has write permissions for the user who's running PHP
   * Remove any limits you may have on core dump size from your shell: 
     * tcsh: unlimit coredumpsize
@@ -15 +15 @@
     * PHP As Apache Module: Run httpd -X, and access the script that crashes PHP
 == Once you have the core file ==
-check where the coredump is
+First, check where the coredump is
+====== Checking where the coredump is ======
 {{{
 #!ShellExample
@@ -23 +24 @@
 /tmp/core
 }}}
-ok, it's there
 
  * 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:
+====== Generating backtrace for PHP as CGI/FastCGI ======
 {{{
 #!ShellExample
@@ -36 +37 @@
 
   * 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:
+====== Generating backtrace for PHP as As Webserver Module ======
 {{{
 #!ShellExample