From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28339 invoked by alias); 8 Nov 2005 01:07:46 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 28315 invoked by uid 48); 8 Nov 2005 01:07:39 -0000 Date: Tue, 08 Nov 2005 01:07:00 -0000 Message-ID: <20051108010739.28314.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug other/24724] _Unwind_Backtrace() calls malloc In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "arun dot sharma at google dot com" X-SW-Source: 2005-11/txt/msg01043.txt.bz2 List-Id: ------- Comment #7 from arun dot sharma at google dot com 2005-11-08 01:07 ------- (In reply to comment #4) > I really doubt we can remove it because this is also used in the undwinding for > exceptions. > It must be possible to do stack unwinding without any mallocs. If the exception throwing code path requires mallocs, that's fine by us. The particular malloc in question is coming from start_fde_sort() in unwind-dw2-fde.c. Perhaps the sorting can be done earlier i.e. before _Unwind_Backtrace() is called? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24724