Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Tue, 10 May 2005 15:43:36 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Static destructors not running Message-ID: <20050510194336.GB32314@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <48781a66050509154660edcc78 AT mail DOT gmail DOT com> <48781a6605051006066aa9b036 AT mail DOT gmail DOT com> <20050510153512 DOT GZ15665 AT trixie DOT casa DOT cgf DOT cx> <48781a66050510085450bd1339 AT mail DOT gmail DOT com> <20050510160904 DOT GF15665 AT trixie DOT casa DOT cgf DOT cx> <48781a66050510122722a2d436 AT mail DOT gmail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48781a66050510122722a2d436@mail.gmail.com> User-Agent: Mutt/1.5.8i On Tue, May 10, 2005 at 03:27:02PM -0400, William M. (Mike) Miller wrote: >On 5/10/05, Christopher Faylor wrote: >> Previous to 1.5.16, static destructors were always called via a >> gcc "atexit" mechanism. This meant that there were scenarios where >> destructors would not be called at all so I made cygwin's exit call >> the destructors explicitly. I just forgot to make cygwin do the right >> thing when returning from main rather than exiting. This will be >> fixed in the next snapshot. > >Sorry, one more question. I thought from the above that >reinstalling 1.5.15 would restore the previous behavior for static >destructors. According to cygcheck, I now have cygwin 1.5.15-1 >installed, but I still don't see the static destructor output. Is there >something else I need to revert while waiting for the fix? Install the snapshot: http://cygwin.com/snapshots/ -- 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/