X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Wed, 20 Apr 2011 15:21:37 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Memory leak in select Message-ID: <20110420132137.GC5842@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <4DAC23E3.2020005@lysator.liu.se> <4DAC2D35.5070106@lysator.liu.se> <4DAC4B6A.50101@lysator.liu.se> <20110418152441.GA12913@ednor.casa.cgf.cx> <20110418152801.GA11182@ednor.casa.cgf.cx> <4DAC8F96.3080808@lysator.liu.se> <4DADFF3A.1060006@lysator.liu.se> <20110420011057.GA453@ednor.casa.cgf.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Apr 20 15:16, Thomas Stalder wrote: > Hello, > > I just have a question, the same change would it not necessary for the > functions: serial_cleanup, mailslot_cleanup and socket_cleanup in > select.cc (like attached patch) ? > > I don't know, it's just a question. The patch are not tested. Maybe you should actually test it. There's a good chance that it fixes your memory issue. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple