From: "William M. (Mike) Miller" <william.m.miller@gmail.com>
To: "André Bleau" <andre_bleau@hotmail.com>
Cc: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Failed assertion dialog box
Date: Sun, 15 Nov 2020 15:59:52 -0500 [thread overview]
Message-ID: <CAH5rLZV7ATu7CJrNUKZQL=76cuvdkUdi7uErkFs0mAHDT7w_sA@mail.gmail.com> (raw)
In-Reply-To: <DM5PR19MB0986B3BF7499FE71262677FB93E40@DM5PR19MB0986.namprd19.prod.outlook.com>
On Sun, Nov 15, 2020 at 3:39 PM André Bleau via Cygwin <cygwin@cygwin.com>
wrote:
>
> On Sat, Nov 14, 2020 at 11:49 PM Duncan Roe <duncan_roe@optusnet.com.au>
> 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é 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=disable_pcon /usr/bin/mintty &
>
> In the newly created window:
>
> $ ./a.exe </dev/null >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 </dev/null >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=%PATH%D:\Cygwin\bin;
> a.exe <NUL: >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!
--
William M. (Mike) Miller | Edison Design Group
william.m.miller@gmail.com
next prev parent reply other threads:[~2020-11-15 21:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 17:27 William M. (Mike) Miller
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 [this message]
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='CAH5rLZV7ATu7CJrNUKZQL=76cuvdkUdi7uErkFs0mAHDT7w_sA@mail.gmail.com' \
--to=william.m.miller@gmail.com \
--cc=andre_bleau@hotmail.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).