This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: SetErrorMode (SEM_FAILCRITICALERRORS) not working on Vista?
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Sat, 26 Apr 2008 10:41:26 +0200
- Subject: Re: SetErrorMode (SEM_FAILCRITICALERRORS) not working on Vista?
- References: <4812566E.4090508@cwilson.fastmail.fm>
- Reply-to: cygwin at cygwin dot com
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.
Thanks for the report,
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/