This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: SetErrorMode
- From: Larry Hall <cygwin-lh at cygwin dot com>
- To: "Benson Margulies" <bim2003 at basistech dot com>, "Cygwin List" <cygwin at cygwin dot com>
- Date: Mon, 22 Mar 2004 11:42:37 -0500
- Subject: RE: SetErrorMode
- References: <E8CC5F35918C084F8DBF32A5161C4003285E0A@mailserver.basistech.net>
- Reply-to: Cygwin List <cygwin at cygwin dot com>
Sounds like it would be good if you could find a minimal test case that
reproduces the problem.
Larry
At 07:16 AM 3/22/2004, you wrote:
>Hmm. I have a Windows 'scheduled job'. It runs a zsh.exe script. It runs
>cygwin GNU make. Things that launch under there get hung with 'critical
>error' dialogs. Even when I add an extra layer of program that calls
>SetErrorMode and then CreateProcess outside the shell script.
>
>The most frequent offenders are Java programs, but I can't find any
>evidence that the Sun JVM calls SetErrorMode.
>
>-----Original Message-----
>From: Larry Hall [mailto:cygwin-lh@cygwin.com]
>Sent: Sunday, March 21, 2004 9:56 PM
>To: Benson Margulies; cygwin@cygwin.com
>Subject: Re: SetErrorMode
>
>
>At 12:52 PM 3/21/2004, you wrote:
>>I'm trying to run some builds under cygwin with SetErrorMode set to
>>avoid Windows dialog boxes in the event of hard errors. I'm failing. I
>>get dialog boxes. Is cygwin doing anything to call SetErrorMode and
>>undo my efforts, or do I need to look elsewhere?
>
>
>You're a little short on details here but to answer your question, the
>code for the Cygwin DLL only makes one call to SetErrorMode() for
>SEM_FAILCRITICALERRORS.
>
>HTH,
>
>
>--
>Larry Hall http://www.rfk.com
>RFK Partners, Inc. (508) 893-9779 - RFK Office
>838 Washington Street (508) 893-9889 - FAX
>Holliston, MA 01746
>
>
>--
>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/
--
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/