X-Spam-Check-By: sourceware.org Date: Tue, 22 Aug 2006 08:43:31 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: WG: Memory Problem with POSIX Thread under Windows XP Message-ID: <20060822124331.GB23690@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <00f601c6c5e0$94cc9720$a501a8c0 AT CAM DOT ARTIMI DOT COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00f601c6c5e0$94cc9720$a501a8c0@CAM.ARTIMI.COM> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Tue, Aug 22, 2006 at 12:46:18PM +0100, Dave Korn wrote: >On 22 August 2006 11:09, Martin J?hren wrote: >>I tried following code with vs2005, and... there is no memory problem! >>So the bug must be located in CYGWIN or in GCC. Form now on it seems >>to me, that I really need help. Cause I'm not so familiar with deeper >>CYGWIN or GCC problems. I'm looking foward for any ideas how to handle >>the problem... > >I would imagine that you need to start looking at newlib. Probably the >per-thread reent structures aren't being freed. This is a WAG, >however. If those aren't being freed then it's probably something in thread.cc. 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/