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 Message-ID: <48781a6605051006066aa9b036@mail.gmail.com> Date: Tue, 10 May 2005 09:06:36 -0400 From: "William M. (Mike) Miller" Reply-To: "William M. (Mike) Miller" To: cygwin AT cygwin DOT com Subject: Re: Static destructors not running In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: <48781a66050509154660edcc78 AT mail DOT gmail DOT com> X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j4AD7ENv029805 On 5/9/05, Dave Korn wrote: > ----Original Message---- > >From: William M. (Mike) Miller > > The output "In dtor." is missing. > > That's because stdout is already closed by the time your dtor runs. I > stepped right into it, it does the printf call but somewhere down in the dll > it checks the flags field in the stdout FILE object for read/write and finds > it's not open for either, so it's at eof. Grep 'cantwrite' if you really > want to find it. > > Anyway, your dtor is called. You're absolutely right -- the destructor is being called. I should have checked that myself, rather than assuming that the absence of its output meant that it was not being executed. Thanks for investigating. I'm still left with the problem of figuring out what changed to cause this result. Until I ran the "setup" application last Friday, I was seeing output from static destructors, and now I don't. It would save me a lot of work to be able to restore the old behavior, but I don't know what was responsible for this change. -- William M. (Mike) Miller | Edison Design Group william DOT m DOT miller AT gmail DOT com -- 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/