X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Mon, 28 Apr 2008 15:11:35 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: SetErrorMode (SEM_FAILCRITICALERRORS) not working on Vista?
Message-ID: <20080428131135.GA31564@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <4812566E DOT 4090508 AT cwilson DOT fastmail DOT fm> <20080426084126 DOT GP23852 AT calimero DOT vinschen DOT de> <20080426180216 DOT GR23852 AT calimero DOT vinschen DOT de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20080426180216.GR23852@calimero.vinschen.de>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

On Apr 26 20:02, Corinna Vinschen wrote:
> On Apr 26 10:41, Corinna Vinschen wrote:
> > On Apr 25 18:08, cygwin AT cwilson DOT fastmail DOT 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

I got a reply from the Microsoft guy.  Known bug:

  http://tinyurl.com/48g4oo


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/