Changes between Version 6 and Version 7 of HowToReportABug

Timestamp:

2007-04-07T03:54:34+02:00 (7 years ago)

Author:

moo

Comment:

--

HowToReportABug

@@ -2 +2 @@
 [[PageOutline]]
 = How To Report A Bug =
-
+== Quick Walkthrough ==
 If you find a bug in XCache, you can help alot to find a fix for it by following some simple steps:
 
@@ -20 +20 @@
 You can check the following sections for instructions on how to do all the steps above.
 
-== Checking System Version ==
+== Long Walkthrough ==
+=== Checking System Version ===
 {{{
 #!ShellExample
@@ -27 +28 @@
 }}}
 
-== Checking gcc/glibc Version ==
+=== Checking gcc/glibc Version ===
 {{{
 #!ShellExample
@@ -37 +38 @@
 }}}
 
-== Checking PHP Version ==
+=== Checking PHP Version ===
 {{{
 #!ShellExample
@@ -57 +58 @@
 }}}
 
-== Generating a Backtrace ==
+=== Generating a Backtrace ===
 
-=== If you don't have a core file yet ===
+==== 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
@@ -70 +71 @@
     * PHP FastCGI: Simply setup normal webserver-fastcgi configuration, and access the script that crashes PHP 
     * PHP As Apache Module: Run httpd -X, and access the script that crashes PHP
-=== Once you have the core file ===
+==== Once you have the core file ====
 check where the coredump is
 {{{
@@ -101 +102 @@
 }}}
 
-== Filing A Bug ==
+=== Filing A Bug ===
 File bug [/xcache/newticket here]. We need as much information as possible. It will greatly helps us tracing it down.
 
-== Submiting A Patch ==
+=== Submiting A Patch ===
 If you've managed to write a patch, you may attach it at [/xcache/newticket here] too. It would helps us a lot if you generate the bug with:
 {{{