Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16226.14655.873792.418770@gargle.gargle.HOWL>
Date: Fri, 12 Sep 2003 16:23:11 -0500
From: Pete McCann <mccap@lucent.com>
To: cygwin@cygwin.com
Subject: Re: SEGV in conv_path_list_buf_size with xemacs-21.5-b13 and cygwin-snapshot-20030904-1
In-Reply-To: <16226.8585.30792.371032@gargle.gargle.HOWL>
References: <20030910085841.GA1859@cygbert.vinschen.de>
	<16215.25725.555006.332144@gargle.gargle.HOWL>
	<16222.14630.498481.227468@gargle.gargle.HOWL>
	<16226.8585.30792.371032@gargle.gargle.HOWL>


(responding to my own post)

Pete McCann writes:
 > 
 > Corinna Vinschen writes:
 > 
 > > On Tue, Sep 09, 2003 at 03:33:42PM -0500, Pete McCann wrote:
 > > > 
 > > > Hi,
 > > > 
 > > > After some more hunting, I now understand there is a difference
 > > > between the cygwin heap and the user heap.  My problem is that I'm
 > > > running out of cygwin heap:
 > > 
 > > Can you check how often the function cygwin_posix_to_win32_path_list_buf_size()
 > > is called?  Does that happen fairly often?
 > > 
 > > Corinna
 > 
 > That function is called about 600 - 700 times (sometimes as many as
 > 2000-3000) when I do a simple operation like checking for new mail in
 > the spool file.  cygheap_max grows steadily with each call.

And, I don't see a destructor for path_conv that would free
normalized_path.  Perhaps this is the source of the memory leak?
Note that a path_conv is created on the stack inside
conv_path_list_buf_size at path.cc, line 3627.

-Pete


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/