From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ej1-x629.google.com (mail-ej1-x629.google.com [IPv6:2a00:1450:4864:20::629]) by sourceware.org (Postfix) with ESMTPS id 9E0BF3851C13 for ; Sun, 15 Nov 2020 13:12:36 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 9E0BF3851C13 Received: by mail-ej1-x629.google.com with SMTP id dk16so20476774ejb.12 for ; Sun, 15 Nov 2020 05:12:36 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=23Ul7+Xf3IQHGDzGt4jbvifv/gykCWDlBFB1noL5zYA=; b=iHMqdoKvroJaH442+uxHiBtk6s0fmuMErwbwyNvPCjcmPGe55fsuXc0qXfdH4IMr3u mO6kCnUamn3Q4Zj2iJDtzk2hbzdONWLnPsABpB+CTAMZPLFF7B498ZLpPzV04Skr+ks3 SDTBljU3QhFBjEB7qhlYCe2r932gEkjiz5V8USrbYP+cjNXa4Rsu1W1vb+a5uA8/yKo/ awOvhDIKlZ2f2r4YFuF0Ey7ZBts/4QLZgu+qA+aaZnxkgy/zryiWssvwmbwIvjq4pnKw RC67CjDQq5r05KjEib+HZgkOiFrDESE2M57K497YzAkTp76S7m8xV6JB2QOEmfszr+3F jhgg== X-Gm-Message-State: AOAM530LTJPRkFMG58vISa/Zyar2MSbSVwkEZjx1L6brGr9YKl6ZRdon rMgYSCo6/ihHm2D32nO7SNU/k/KVHG9I4Jrtx5VOx+1wN9Y= X-Google-Smtp-Source: ABdhPJxr4LQWIgr/OD79UXFN6GGM3/oePvm6lVIx7RWx+nPd+xSulH11u83AwY0HxpHnmPWxJA38E2JksmaPISwOb7M= X-Received: by 2002:a17:906:f207:: with SMTP id gt7mr10585066ejb.293.1605445955328; Sun, 15 Nov 2020 05:12:35 -0800 (PST) MIME-Version: 1.0 References: <20201114034504.GD2905@dimstar.local.net> <20201115044613.GE2905@dimstar.local.net> In-Reply-To: <20201115044613.GE2905@dimstar.local.net> From: "William M. (Mike) Miller" Date: Sun, 15 Nov 2020 08:12:23 -0500 Message-ID: Subject: Re: Failed assertion dialog box To: The Cygwin Mailing List X-Spam-Status: No, score=-2.3 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Nov 2020 13:12:38 -0000 On Sat, Nov 14, 2020 at 11:49 PM Duncan Roe wrote: > On Fri, Nov 13, 2020 at 11:21:12PM -0500, cygwin wrote: > > On Fri, Nov 13, 2020 at 10:45 PM Duncan Roe > > wrote: > > > > > Hi William, > > > > > > On Fri, Nov 13, 2020 at 12:27:57PM -0500, cygwin wrote: > > > > I've run into a problem running a collection of tests under Cygwin > and I > > > > wonder if anyone can suggest a way around it. > > > > > > > > The problem occurs when a program being run fails a C/C++ runtime > > > > assertion. Ordinarily, this just writes an error message on stderr > and > > > > aborts. Under Cygwin, however, if both stdin and stderr are > redirected to > > > > files, the program instead pops up a dialog box that must be > > > interactively > > > > dismissed before the failed program will exit - holding up all the > tests > > > > that follow it. > > > > > > > > Specifically, if I have the following as assert.cpp: > > > > > > > > #include > > > > int main() { > > > > assert(false); > > > > } > > > > > > > > and say > > > > > > > > gcc assert.cpp > > > > ./a.exe < /dev/null > output 2>&1 > > > > > > > > I get an error dialog box saying > > > > > > > > Failed assertion > > > > false > > > > at line 3 of file assert.cpp > > > > in function int main() > > > > > > > > If I omit either the stdin or the stderr redirection, the program > behaves > > > > as desired with no dialog box. > > > > > > > > Is there an environment setting or compiler command-line option I can > > > give > > > > to suppress the dialog box and always just write a message to stderr > and > > > > abort? Thanks for any insights. > > > > > > Your example WFFM, (Cygwin64, gcc 10.2.0, everything else also up to > date). > > > > > > Do you still see this behaviour if you run the installer? > > > > > > > Thanks for your reply; unfortunately, yes, it does. I had refreshed > > the installation fairly recently, and running the installer only updated > a > > few things, not cygwin.dll and not gcc; my installation is the same as > > yours. I've tried it with three different shells (tcsh, bash, mksh) and > > with both gcc and clang, and all have the same behavior. (Interestingly, > if > > I compile the example with MSVC and run it in a Cygwin shell, it does > _not_ > > pop up an error dialog box, so presumably it's in the Cygwin runtime, > > specifically the definition of __assert_func.) > > Sorry, should have mentioned running on Win7 Home. > > When I try it on my wife's Win10 system, I get the dialog box same as you. > That's disappointing. Thanks for the additional information, though. -- William M. (Mike) Miller | Edison Design Group william.m.miller@gmail.com