On Apr 26 20:02, Corinna Vinschen wrote: > On Apr 26 10:41, Corinna Vinschen wrote: > > On Apr 25 18:08, [EMAIL PROTECTED] 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/
