svn commit: r1895246 - /httpd/site/trunk/content/dev/debugging.mdtext

[co...@apache.org]

Author: covener
Date: Sun Nov 21 18:14:00 2021
New Revision: 1895246

URL: http://svn.apache.org/viewvc?rev=1895246&view=rev
Log:
mention procdump on Windows

Modified:
    httpd/site/trunk/content/dev/debugging.mdtext

Modified: httpd/site/trunk/content/dev/debugging.mdtext
URL: http://svn.apache.org/viewvc/httpd/site/trunk/content/dev/debugging.mdtext?rev=1895246&r1=1895245&r2=1895246&view=diff
==============================================================================
--- httpd/site/trunk/content/dev/debugging.mdtext (original)
+++ httpd/site/trunk/content/dev/debugging.mdtext Sun Nov 21 18:14:00 2021
@@ -246,6 +246,7 @@ dumping all thread contexts, your log an
 type. (Full is quite large, but necessary sometimes for a programmer-type
 to load your crash dump into a debugger and begin unwinding exactly what
 has happened. Mini is sufficient for your first pass through the process.)
+You may alternatively use "procdump" from Sysinternals
 
 1. Note that if you previously installed and then uninstalled other
 debugging software, you may need to invoke `drwtsn32 -i` in order to make
@@ -271,6 +272,8 @@ the ThreadsPerChild directive.) The proc
 
 1. Using the {pid} number you noted above, invoke the command
 > `drwtsn32 -p {pid}` 
+or
+> `prodcump {pid}`
 
 Voila, you will find in your 'log file path' a `drwtsn32.log` file, and if
 you choose to 'append to existing log file', jump through the 'App:'