Mon Mar 22 20:45:00 GMT 2004
Sounds like it would be good if you could find a minimal test case that
reproduces the problem.
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.
>From: Larry Hall [mailto:firstname.lastname@example.org]
>Sent: Sunday, March 21, 2004 9:56 PM
>To: Benson Margulies; email@example.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
>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
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
More information about the Cygwin