* Cygwin and stdexcept bug ? [not found] <CGME20191009091114eucas1p147c56151289433e66189371bb647eb89@eucas1p1.samsung.com> @ 2019-10-09 9:11 ` Pavel Fedin 2019-10-10 11:07 ` Takashi Yano 0 siblings, 1 reply; 2+ messages in thread From: Pavel Fedin @ 2019-10-09 9:11 UTC (permalink / raw) To: cygwin Hello everyone! On Linux if a C++ application throws uncaught error, there's explanation given: --- cut --- terminate called after throwing an instance of 'std::runtime_error' what(): Just throw up Aborted --- cut --- On 64-bit Cygwin the same code simply silently aborts, giving no hints. I've tried on 32 bits; everything seems to work. However i haven't updated my 32-bit install for ages; may be something has changed. Is it a bug or feature? My test code is: --- cut --- #include <stdexcept> #include <iostream> int main(void) { throw std::runtime_error("Just throw up"); std::cout << "What ???\n"; return 0; } --- cut --- Kind regards, Pavel Fedin Senior Engineer Samsung Electronics Research center Russia -- 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 ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Cygwin and stdexcept bug ? 2019-10-09 9:11 ` Cygwin and stdexcept bug ? Pavel Fedin @ 2019-10-10 11:07 ` Takashi Yano 0 siblings, 0 replies; 2+ messages in thread From: Takashi Yano @ 2019-10-10 11:07 UTC (permalink / raw) To: cygwin On Wed, 9 Oct 2019 12:11:13 +0300 "Pavel Fedin" wrote: > Hello everyone! > > On Linux if a C++ application throws uncaught error, there's explanation given: > --- cut --- > terminate called after throwing an instance of 'std::runtime_error' > what(): Just throw up > Aborted > --- cut --- > > On 64-bit Cygwin the same code simply silently aborts, giving no hints. I've tried on 32 bits; everything seems to work. However i > haven't updated my 32-bit install for ages; may be something has changed. > Is it a bug or feature? > > My test code is: > --- cut --- > #include <stdexcept> > #include <iostream> > > int main(void) > { > throw std::runtime_error("Just throw up"); > std::cout << "What ???\n"; > return 0; > } > --- cut --- I confirmed this problem is not a pseudo console related issue. This occurs even with Cygwin 3.0.7 (x86_64). -- 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 ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-10-10 11:07 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <CGME20191009091114eucas1p147c56151289433e66189371bb647eb89@eucas1p1.samsung.com>
2019-10-09 9:11 ` Cygwin and stdexcept bug ? Pavel Fedin
2019-10-10 11:07 ` Takashi Yano
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).