Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Fri, 25 Feb 2000 19:57:39 -0500 To: Sean Champ Cc: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: "garbage collection" Message-ID: <20000225195739.A2832@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com References: <002001bf7ff0$8c37a9c0$99591c3f AT toolbox> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.4i In-Reply-To: <002001bf7ff0$8c37a9c0$99591c3f@toolbox>; from symmetry_web@email.msn.com on Fri, Feb 25, 2000 at 04:29:30PM -0800 On Fri, Feb 25, 2000 at 04:29:30PM -0800, Sean Champ wrote: >...is there any way to take a look at what's been left in memory, after a >leaky piece of software has been shut down? Um, AFAICT, this is not a question for cygwin-developers. Is there something specific to the cygwin DLL lurking in this question? cgf