From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: assert does not show output in cygwin test build
Date: Wed, 09 Oct 2019 10:54:00 -0000 [thread overview]
Message-ID: <20191009195427.28daf789b85b0e0333b05b74@nifty.ne.jp> (raw)
In-Reply-To: <001901d57e8d$dc665480$9532fd80$@samsung.com>
On Wed, 9 Oct 2019 13:39:42 +0300
"Pavel Fedin" wrote:
> Hello!
>
> > Thanks for your report. However, I cannot reproduce the problem.
> >
> > 1. Could you please describe the steps to reproduce this?
>
> g++ test.cpp -o test
> ./test
>
> > 2. What happens if you execute:
> > ./a.exe 2>&1 | cat
>
> The same. No output.
> From gdb i know that the control reaches __cxa_throw and then RaiseException(). Then the app apparently just exits.
>
> I'll try to debug this myself when i have some time.
Is this surely the reply to "Re: assert does not show output in
cygwin test build" ?
Or your reply is regarding "Cygwin and stdexcept bug ?" ?
--
Takashi Yano <takashi.yano@nifty.ne.jp>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-10-09 10:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 7:16 Biswapriyo Nath
2019-10-09 10:03 ` Takashi Yano
2019-10-09 10:39 ` Pavel Fedin
2019-10-09 10:54 ` Takashi Yano [this message]
2019-10-09 11:27 ` Pavel Fedin
2019-10-09 12:39 ` Biswapriyo Nath
2019-10-09 15:31 ` assert creates unusable core dump on current stable Cygwin release Brian Inglis
2019-10-09 17:10 ` Jon Turney
2019-10-09 21:28 ` Brian Inglis
2019-10-10 19:19 ` Jon Turney
2019-10-10 20:57 ` Csaba Raduly
2019-10-10 22:20 ` Brian Inglis
2019-10-13 16:27 ` Jon Turney
2019-10-13 18:14 ` Brian Inglis
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=20191009195427.28daf789b85b0e0333b05b74@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).