From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26483 invoked by alias); 17 Oct 2010 13:58:22 -0000 Received: (qmail 26474 invoked by uid 22791); 17 Oct 2010 13:58:21 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 17 Oct 2010 13:58:16 +0000 From: "alserkli at inbox dot ru" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/46056] New: range-based for loop inside lambda crashes if _GLIBCXX_DEBUG is defined X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: alserkli at inbox dot ru X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Sun, 17 Oct 2010 13:58:00 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-10/txt/msg01400.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46056 Summary: range-based for loop inside lambda crashes if _GLIBCXX_DEBUG is defined Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: alserkli@inbox.ru Target: i686-pc-linux-gnu The following test crashes once compiled by g++ (GCC) 4.6.0 20101017 (experimental) on i686-pc-linux-gnu // Test for range-based for loop inside lambda // { dg-options "-std=c++0x" } // { dg-do run } #define _GLIBCXX_DEBUG #include #include int main(){ std::vector v(1); [&]() { for(auto i: v); }(); } Apparently it crashes during safe sequence destruction once main is finished. It does work (i.e., does not crash) without any one of _GLIBCXX_DEBUG, lambda, or range-based for. Also, it does not crash if optimization is on (e.g., with -O).