From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ej1-x630.google.com (mail-ej1-x630.google.com [IPv6:2a00:1450:4864:20::630]) by sourceware.org (Postfix) with ESMTPS id 5DE3D3858C27 for ; Sun, 15 Nov 2020 21:00:05 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 5DE3D3858C27 Received: by mail-ej1-x630.google.com with SMTP id i19so21575262ejx.9 for ; Sun, 15 Nov 2020 13:00:05 -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:cc; bh=hR5Fh4qTEoM5rfYTDofnfG5GtMC1CgZY5phfDeUZMNo=; b=oiJOk7rRl9FrxYMAeMbQTbyatMXBOTLLQHM6R+KDWTaOgDc9jnUPnO6YMLfknEgQQ3 EOniP+FSGK4Nzcg93Bq4KpU+N6mKOX81TAPY99ReL63X3BBs4/W1fSP8iOdcf7oPyND/ eDpONZdFnzm7uKwF1LTViU11KtSdhK1Chp8BxGLMinEw8X0b1q6Koxkolk7V3Jv7fnGW L3D+3wLLFQwC6s/QiFjRXt1aShbWp0gWhP58XkXBl+9aR0mqT1JDeyup/eRyXExzg+Gi 3FvpHotyEuonmDZWvI311DpaoLpGlCUwXzfDpY3fscjq6Tm4mzdY0B+aS9iI1t1IC3ZV zULA== X-Gm-Message-State: AOAM533YBqIiwyx74CcO9/w3/zCc5Oc5nn5Y7PtAZWK8Y7dC/7fbQelc 3qhlcG5sRgK8r2VEB8rBaMMZz4Rf987Ip3vj+JE= X-Google-Smtp-Source: ABdhPJyzpAvFqHw+Emlz5EjXPZY00P/vrgR+cGUocJGRA24PDvv9yVvVzvRZtq8t4acpZFja2mj/dMrIuFBnZwEXCcQ= X-Received: by 2002:a17:907:1112:: with SMTP id qu18mr12069557ejb.507.1605474004433; Sun, 15 Nov 2020 13:00:04 -0800 (PST) MIME-Version: 1.0 References: <20201114034504.GD2905@dimstar.local.net> <20201115044613.GE2905@dimstar.local.net> In-Reply-To: From: "William M. (Mike) Miller" Date: Sun, 15 Nov 2020 15:59:52 -0500 Message-ID: Subject: Re: Failed assertion dialog box To: =?UTF-8?B?QW5kcsOpIEJsZWF1?= Cc: The Cygwin Mailing List X-Spam-Status: No, score=-2.9 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" Content-Transfer-Encoding: quoted-printable 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 21:00:07 -0000 On Sun, Nov 15, 2020 at 3:39 PM Andr=C3=A9 Bleau via Cygwin wrote: > > On Sat, Nov 14, 2020 at 11:49 PM Duncan Roe > wrote: > > ... > > > > > 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. > > -------------------------------------------------------------------------= -------------- > > I would say we got some useful info: > 1- The bug is OS specific; it occurs in Windows 10 > 2- Three persons were able to reproduce it on Windows 10, which improves > the probability of getting fixed. > > - Andr=C3=A9 Bleau > > -------------------------------------------------------------------------= -------------- > > Here's some more info: > > It seems the bug is related to pseudo-console support; that explains why > it is Windows 10 specific. > > Experiment: > > CYGWIN=3Ddisable_pcon /usr/bin/mintty & > > In the newly created window: > > $ ./a.exe output.txt 2>&1 > Aborted (core dumped) > > No message box popup. > > $ cat output.txt > assertion "false" failed: file "assert.cpp", line 3, function: int main() > > In the original mintty window, with empty CYGWIN env variable: > > $ ./a.exe output.txt 2>&1 > Aborted (core dumped) > > A message box pops > > AND: > > $ cat output.txt > > output.txt is empty > > So, 2 problems here. > > In a CMD Window: > > set path=3D%PATH%D:\Cygwin\bin; > a.exe outcmd.txt 2>&1 > 1 [main] a 759 cygwin_exception::open_stackdumpfile: Dumping stack > trace to a.exe.stackdump > type outcmd.txt > assertion "false" failed: file "assert.cpp", line 3, function: int main() > 1 [main] a 759 cygwin_exception::open_stackdumpfile: Dumping stack > trace to a.exe.stackdump > > The bug could be in cygwin or in mintty. Maybe this is something that > Thomas Wolff (mintty author) or Takashi Yano (pseudo-console support > expert) would want to look at. > That seems like useful information. However, my experience is a bit different; I get the popup regardless of whether the CYGWIN environment variable is empty or disable_pcon. However, I do see the same behavior as you with regard to mintty versus a command shell window, so I think that would argue in favor of mintty being responsible for popping up the dialog. Thanks for the information! --=20 William M. (Mike) Miller | Edison Design Group william.m.miller@gmail.com