X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Sat, 26 Apr 2008 10:41:26 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: SetErrorMode (SEM_FAILCRITICALERRORS) not working on Vista? Message-ID: <20080426084126.GP23852@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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4812566E.4090508@cwilson.fastmail.fm> 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: List-Unsubscribe: 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 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. 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/