httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1050812 - /httpd/site/trunk/xdocs/dev/debugging.xml
Date Sun, 19 Dec 2010 11:21:11 GMT
Author: igalic
Date: Sun Dec 19 11:21:11 2010
New Revision: 1050812

Fixing links and removing some *very* *old* references.


Modified: httpd/site/trunk/xdocs/dev/debugging.xml
--- httpd/site/trunk/xdocs/dev/debugging.xml [utf-8] (original)
+++ httpd/site/trunk/xdocs/dev/debugging.xml [utf-8] Sun Dec 19 11:21:11 2010
@@ -10,7 +10,7 @@
 <title>Apache Debugging Guide</title>
 <p>This document is a collection of notes regarding tools and techniques
-for debugging Apache and Apache modules.</p>
+for debugging Apache httpd and its modules.</p>
 <p>Got more tips?  Send 'em to
 <a href=""></a>.  Thanks!</p>
@@ -31,7 +31,7 @@ for debugging Apache and Apache modules.
 <section id="gdb">
 <title>Using gdb</title>
-<p>If you use the gcc or egcs compilers, it is likely that the best
+<p>If you use the gcc compiler, it is likely that the best
 debugger for your system is gdb.  This is only a brief summary of how
 to run gdb on Apache -- you should look at the info and man files for
 gdb to get more information on gdb commands and common debugging techniques.
@@ -145,10 +145,9 @@ working directory and using the server r
 <li>use the "<code>p</code>" command to print the value of a variable.</li>
-<p>A file in the <code>src/</code> directory (1.3) or the root directory
-(2.x) called <code>.gdbinit</code> provides useful macros for printing
-out various internal structures of httpd like tables (<code>dump_table</code>),
-brigades (<code>dump_brigade</code>) and filter chains
+<p>A file in the the root directory called <code>.gdbinit</code> provides
+useful macros for printing out various internal structures of httpd like tables
+(<code>dump_table</code>), brigades (<code>dump_brigade</code>) and
filter chains
 <p>If you are debugging a repeatable crash, simply run gdb as above
@@ -178,7 +177,7 @@ occurred during processing.</p>
 were called to get to a particular point in the process.  On some platforms
 you can get a live backtrace of any process.</p>
-<p>For SVR4-based variants of Unix, the pstack command for proc can
+<p>For SVR4-based variants of Unix, the <code>pstack<code> command for
proc can
 be used to display a a live backtrace.  For example, on Solaris it looks 
@@ -297,7 +296,7 @@ dumps which can be analyzed further.</p>
 <p>To ensure that a core dump is written to a directory which is
 writable by the user which child processes run as (such as
 <code>apache</code>), the <a
 directive must be added to <code>httpd.conf</code>; for example:</p>
@@ -441,12 +440,12 @@ At this point you can use:</p>
 <section id="sol27">
 <title>Solaris and coredumps</title>
-<p>On Solaris (at least 2.7 and up) use <b><code>coreadm</code></b>
to make
+<p>On Solaris use <b><code>coreadm</code></b> to make
 <code>setuid()</code> processes actually dump core. By default a setuid()
 process does not dump core. This is the reason why httpd servers started as
 root with child processes running as a different user (such as
 <code>apache</code>) do not coredump even when the
-<a href="">
+<a href="">
 directive had been set to an appropriate and writable directory and
 <b><code>ulimit -c</code></b> has a sufficient size. See also
@@ -499,7 +498,7 @@ allows the analysis of the sniffed data.
 <p>There is also a simple ASCII viewer for TCP dump traces in the Apache
 repository in the file
-<a href="">
+<a href="">

View raw message