From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20872 invoked by alias); 8 Jan 2013 21:53:27 -0000 Received: (qmail 20864 invoked by uid 22791); 8 Jan 2013 21:53:26 -0000 X-SWARE-Spam-Status: No, hits=-5.3 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-lb0-f178.google.com (HELO mail-lb0-f178.google.com) (209.85.217.178) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 08 Jan 2013 21:53:21 +0000 Received: by mail-lb0-f178.google.com with SMTP id l5so735383lbo.23 for ; Tue, 08 Jan 2013 13:53:20 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.49.97 with SMTP id t1mr26624277lbn.58.1357681999941; Tue, 08 Jan 2013 13:53:19 -0800 (PST) Received: by 10.112.125.71 with HTTP; Tue, 8 Jan 2013 13:53:19 -0800 (PST) In-Reply-To: References: <50EC4D9E.3070703@ringis.se> <50EC9207.20100@gmail.com> Date: Tue, 08 Jan 2013 22:19:00 -0000 Message-ID: Subject: Re: Problem with noexcept and incomplete backtrace From: Jonathan Wakely To: =?ISO-8859-1?Q?=C1ngel_Gonz=E1lez?= Cc: =?ISO-8859-1?Q?Tobias_Ringstr=F6m?= , gcc-help@gcc.gnu.org Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2013-01/txt/msg00063.txt.bz2 On 8 January 2013 21:48, Jonathan Wakely wrote: > Tobias, please report it to bugzilla. The standard places no > requirements on what happens except that std::terminate is called but > even if it's not a bug there is room for improvement. I was a bit hasty, the standard does place some requirements: In the situation where the search for a handler (15.3) encounters the outermost block of a function with a noexcept-specification that does not allow the exception (15.4), it is implementation-defined whether the stack is unwound, unwound partially, or not unwound at all before std::terminate() is called. In all other G++ appears to partially unwind the stack, although that isn't documented at http://gcc.gnu.org/onlinedocs/gcc/Exception-handling.html