From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 98314 invoked by alias); 10 Oct 2019 11:07:28 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 98292 invoked by uid 89); 10 Oct 2019 11:07:28 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-10.1 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_2,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=HX-Languages-Length:919 X-HELO: conssluserg-06.nifty.com Received: from conssluserg-06.nifty.com (HELO conssluserg-06.nifty.com) (210.131.2.91) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 10 Oct 2019 11:07:26 +0000 Received: from Express5800-S70 (ntsitm283243.sitm.nt.ngn.ppp.infoweb.ne.jp [125.1.151.243]) (authenticated) by conssluserg-06.nifty.com with ESMTP id x9AB7L2W032035 for ; Thu, 10 Oct 2019 20:07:21 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-06.nifty.com x9AB7L2W032035 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.ne.jp; s=dec2015msa; t=1570705641; bh=ZF/jyUqEIoI0TrrxgxDISeuCOrRdJsOTwbphaNTjQJE=; h=Date:From:To:Subject:In-Reply-To:References:From; b=D6TrQZiC/aBI+5p8wD8riGItsMF5+syaLyJ3kIxPofXVCdgNKL3JlHuTK+HSAjxtx uW6OCh2iua8RZZ0enZWBpplErXSlsHVoBRXpX7P+8vy+cQi4IFn//fByKSKBCU/7ut LSmu9lNKtw5S+3UsSjyohd57iFp02jQEs18mIFb7SuySGp9R/QBKQoAN/BL7F1FwKE TS9Xl25wrwCf+eJKNwXZL4Az/xtL+W60E3lB9RLskeE1BefdADPYzT8itKyGYk90Fv XBiNttWrMW4X5XmatZBsiKWGsTaTC6sXRXxNs3rALfx4TxSTwa090H+G7ao2pSU570 m4S4I80sTQarQ== Date: Thu, 10 Oct 2019 11:07:00 -0000 From: Takashi Yano To: cygwin@cygwin.com Subject: Re: Cygwin and stdexcept bug ? Message-Id: <20191010200723.db9f1cd19883a987e198eca4@nifty.ne.jp> In-Reply-To: <000001d57e81$800611a0$801234e0$@samsung.com> References: <000001d57e81$800611a0$801234e0$@samsung.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-10/txt/msg00055.txt.bz2 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 > #include > > 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 -- 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