Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
To: dev@apr.apache.org
Path: not-for-mail
From: Ian Holsman <ianh@apache.org>
Newsgroups: server.http.apr.dev
Subject: Re: [PATCH] APR_DEBUG_BUCKET option
Date: Fri, 14 Dec 2001 08:57:29 -0800
Organization: Holsman.NET
Lines: 35
Message-ID: <3C1A2F79.1040302@apache.org>
References: <Pine.LNX.4.33.0112140208330.24983-100000@localhost.localdomain>
NNTP-Posting-Host: int.holsman.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Date: Fri, 14 Dec 2001 16:58:24 +0000 (UTC)
To: Cliff Woolley <cliffwoolley@yahoo.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:0.9.6+) Gecko/20011214

Cliff Woolley wrote:

>    Hmmm... it's too bad that this adds so many #ifdefs to code that's
> largely #ifdef free...  I guess I can see some instances where this would
> be helpful, but I'm not sure it's worth cluttering up all the buckets code
> for.  I'm trying to think of another way to get roughly the same
> information without all the mess.  What if we did it at bucket-insertion
> time?  That way you'd only have to change the brigade insert macros.  A
> bucket that never got inserted into a brigade can't hurt you (except to
> leak memory ;) anyway.  And actually, knowing when a particular bucket got
> stuck in the brigade it's currently in is also valuable information...
> 

Thats a probably a better way.
and will be much more helpful.

(and justin.. I haven't tried it yet)
so far it is looking like it is somewhere in mod-include and
a bucket not on a brigade or something. (brian and jin were debugging 
this late last night)


> --Cliff
> 
> --------------------------------------------------------------
>    Cliff Woolley
>    cliffwoolley@yahoo.com
>    Charlottesville, VA
> 
> 
> 
> 
>