dgaudet     97/10/14 17:24:06

  Modified:    htdocs/manual new_features_1_3.html
               src      CHANGES
  Log:
  Document alloc debugging.
  
  Revision  Changes    Path
  1.27      +10 -0     apachen/htdocs/manual/new_features_1_3.html
  
  Index: new_features_1_3.html
  ===================================================================
  RCS file: /export/home/cvs/apachen/htdocs/manual/new_features_1_3.html,v
  retrieving revision 1.26
  retrieving revision 1.27
  diff -u -r1.26 -r1.27
  --- new_features_1_3.html     1997/10/07 19:44:36     1.26
  +++ new_features_1_3.html     1997/10/15 00:24:01     1.27
  @@ -395,6 +395,16 @@
       An option to <code>spawn_child</code> functions which prevents Apache
       from aggressively trying to kill off the child.
   
  +    <li><strong><code>alloc debugging code</code></strong><br>
  +    Defining <code>ALLOC_DEBUG</code> provides a rudimentary memory
  +    debugger which can be used on live servers with low impact --
  +    it sets all allocated and freed memory bytes to 0xa5.  Defining
  +    <code>ALLOC_USE_MALLOC</code> will cause the alloc code to use
  +    <code>malloc()</code> and <code>free()</code> for each object.  This
  +    is far more expensive and should only be used for testing with tools
  +    such as Electric Fence and Purify.  See <code>main/alloc.c</code>
  +    for more details.
  +
       </ul>
   
   </ul>
  
  
  
  1.463     +8 -0      apachen/src/CHANGES
  
  Index: CHANGES
  ===================================================================
  RCS file: /export/home/cvs/apachen/src/CHANGES,v
  retrieving revision 1.462
  retrieving revision 1.463
  diff -u -r1.462 -r1.463
  --- CHANGES   1997/10/07 20:04:58     1.462
  +++ CHANGES   1997/10/15 00:24:03     1.463
  @@ -1,5 +1,13 @@
   Changes with Apache 1.3b1
   
  +  *) Add debugging code to alloc.c.  Defining ALLOC_DEBUG provides a
  +     rudimentary memory debugger which can be used on live servers with
  +     low impact -- it sets all allocated and freed memory bytes to 0xa5.
  +     Defining ALLOC_USE_MALLOC will cause the alloc code to use malloc()
  +     and free() for each object.  This is far more expensive and should
  +     only be used for testing with tools such as Electric Fence and
  +     Purify.  See main/alloc.c for more details.  [Dean Gaudet]
  +
     *) Configure uses a sh trap and didn't set its exitcode properly.
        [Dean Gaudet] PR#1159
   
  
  
  

Reply via email to