From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26765 invoked by alias); 8 Jan 2015 09:43:57 -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 Received: (qmail 26724 invoked by uid 48); 8 Jan 2015 09:43:52 -0000 From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/64535] New: Emergency buffer for exception allocation too small Date: Thu, 08 Jan 2015 09:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-01/txt/msg00438.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64535 Bug ID: 64535 Summary: Emergency buffer for exception allocation too small Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: rguenth at gcc dot gnu.org It was reported to us that in a heavily threaded environment the number of emergency EH objects in libsubc++ eh_alloc.cc is too small (64). To mitigate this it looks like we could use a TLS variable for the buffer instead (libstdc++ already contains TLS variables for __once_call at least), which also would get rid of the scoped lock (which hopefully will never allocate memory...?). If you use exceptions to catch and recover from low-memory situations __cxa_allocate_exception calling std::terminate () becomes a correctness issue (not sure what the C++ standard says about throwing exceptions in low-memory situations).