Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: SetErrorMode Date: Mon, 22 Mar 2004 07:16:48 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Benson Margulies" To: "Cygwin List" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id i2MCH9aN023609 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/