Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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 11:35:12 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Static destructors not running
Message-ID: <20050510153512.GZ15665@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <48781a66050509154660edcc78 AT mail DOT gmail DOT com> <SERRANONlJbSorxTjtR000002ab AT SERRANO DOT CAM DOT ARTIMI DOT COM> <48781a6605051006066aa9b036 AT mail DOT gmail DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <48781a6605051006066aa9b036@mail.gmail.com>
User-Agent: Mutt/1.5.8i

On Tue, May 10, 2005 at 09:06:36AM -0400, William M. (Mike) Miller wrote:
>On 5/9/05, Dave Korn <dave DOT korn AT artimi DOT com> 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.

Just as a wild guess, does explicitly calling exit help at all?

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/