Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 61815 invoked by uid 500); 30 Jun 2003 22:44:17 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 61804 invoked from network); 30 Jun 2003 22:44:17 -0000 From: "Sander Striker" To: "ranier" , Subject: RE: [PACTH] debug ideas for memory allocation Date: Tue, 1 Jul 2003 00:44:23 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <3EFFAE39.5080807@cultura.com.br> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > From: ranier [mailto:ranier@cultura.com.br] > Sent: Monday, June 30, 2003 5:28 AM > I read a Steve Maguire book named "Guia Microsoft para o desenvolvimento > de programas > sem erros" [ironic not?] and add some ideas for debugging memory > allocation in apr_pool.c. > > 1. Memory not initialized or freed is trash, on debug force this! > 2. Use intensive of the function "assert" on debug development. Using pools debug mode in combination with tools like valgrind have worked wonders. I personally don't think this will add extra value. Sander