delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2005/06/05/21:33:13

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Sun, 5 Jun 2005 21:32:59 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Problem with pthreads (serious memory leaks)
Message-ID: <20050606013259.GA7319@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <BAY107-F1380FDEBFBCDF909067371D6FB0 AT phx DOT gbl>
Mime-Version: 1.0
In-Reply-To: <BAY107-F1380FDEBFBCDF909067371D6FB0@phx.gbl>
User-Agent: Mutt/1.5.8i

On Mon, Jun 06, 2005 at 12:37:14AM +0000, Arash Partow wrote:
>I'm encountering some memory leaks when using pthreads under cygwin.
>As usual the code has been compiled/run on other *nixes (openbsd3.7,
>netbsd2.0 and mandrake10.1) and the leak does not seem to occur.
>
>The system specs are as follows:
>
>1.) gcc 3.3.3
>2.) cygwin dll, snapshots as of:
>   3/6, 1/6, 28/5, 24/5
>   (all produce the same result - haven't test earlier version to
>   see where the break comes from.)
>3.) WinXP Pro SP2 and WinXP Pro 64 SP1
>4.) Dual AMD 64 4k
>5.) 4 gig RAM
>
>
>Example code can be found here:
>
>url:
>http://www.partow.net/downloads/producer-consumer-source.zip
>
>
>To make and run do the following
>
>make all
>
>./example1
>
>using taskmanager or sysinternals or taskinfo one can see that
>there is a huge amount of memory being leaked within cygwin1.dll

How would you come to the conclusion that something is being "leaked"?

>the other examples demonstrate the same effect but much quicker.
>
>any ideas on whats going on?

You'll probably going to have to:

1) Use precise language to describe your problem.

2) Produce a simple(r) test case which demonstrates it.

...if you truly want this fixed.  Perhaps I'm wrong, but I don't think
that anyone is going to want to debug a large application to figure out
what or if the problem is.

cgf

--
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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019