public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "William M. (Mike) Miller" <william.m.miller@gmail.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Failed assertion dialog box
Date: Fri, 13 Nov 2020 12:27:57 -0500	[thread overview]
Message-ID: <CAH5rLZVNLkwntpF4U-27+KeF_eh30yc2bij_MqejWTxBbdQmdw@mail.gmail.com> (raw)

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 <assert.h>
    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.

-- 
William M. (Mike) Miller | Edison Design Group
william.m.miller@gmail.com

             reply	other threads:[~2020-11-13 17:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13 17:27 William M. (Mike) Miller [this message]
2020-11-14  3:45 ` Duncan Roe
2020-11-14  4:21   ` William M. (Mike) Miller
2020-11-14  4:37     ` André Bleau
2020-11-14  5:37       ` Lemures Lemniscati
2020-11-14 14:12         ` William M. (Mike) Miller
2020-11-14 15:24           ` Lemures Lemniscati
2020-11-14 15:53             ` William M. (Mike) Miller
2020-11-15  4:46     ` Duncan Roe
2020-11-15 13:12       ` William M. (Mike) Miller
2020-11-15 20:04         ` André Bleau
2020-11-15 20:39           ` André Bleau
2020-11-15 20:59             ` William M. (Mike) Miller
2020-11-19 14:21             ` Failed assertion dialog box ATTN: Takashi Yano André Bleau
2020-11-19 18:30               ` Thomas Wolff
2020-11-19 21:53                 ` André Bleau
2020-11-20  0:06                 ` Duncan Roe
2020-11-20  0:19                   ` Takashi Yano
2020-11-20  1:40                     ` Duncan Roe
2020-11-20  2:04                     ` Duncan Roe
2020-11-20  7:09                       ` Thomas Wolff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAH5rLZVNLkwntpF4U-27+KeF_eh30yc2bij_MqejWTxBbdQmdw@mail.gmail.com \
    --to=william.m.miller@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).