Date: Sat, 26 Apr 2008 20:02:16 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: SetErrorMode (SEM_FAILCRITICALERRORS) not working on Vista?
Message-ID: <20080426180216.GR23852@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <4812566E.4090508@cwilson.fastmail.fm> <20080426084126.GP23852@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20080426084126.GP23852@calimero.vinschen.de>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Apr 26 10:41, Corinna Vinschen wrote:
> On Apr 25 18:08, cygwin@cwilson.fastmail.fm wrote:
> > So I understand why there are (multiples of) six failures each -- these 
> > relinked versions in the old test suite (and the occurances in the new test 
> > suite) are expected to fail with either dll-not-found or missing-symbol 
> > errors.  But Cygwin calls
> >   SetErrorMode (SEM_FAILCRITICALERRORS)
> > so I don't understand why I'm getting the popups at all.
> >
> > I do /not/ see these popups on WinXPsp2 (cygwin-1.5.25-12)
> 
> I can reproduce that.  I even patched the Cygwin DLL locally so that
> SetErrorMode (SEM_FAILCRITICALERRORS) is called *again*, right before
> calling CreateProcess, but the box still pops up on Vista (well, 2K8
> in my test, actually).  Looks like a bug or "feature" in Vista/2K8.
> I'll investigate further.

FYI: http://tinyurl.com/4xu9y4


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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/