From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4407 invoked by alias); 23 Apr 2010 22:40:30 -0000 Received: (qmail 4360 invoked by alias); 23 Apr 2010 22:40:13 -0000 Date: Fri, 23 Apr 2010 22:40:00 -0000 Message-ID: <20100423224013.4359.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug debug/43828] Emit debug info allowing inlined functions to show in stack traces In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "wilson at codesourcery dot com" 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-04/txt/msg02551.txt.bz2 ------- Comment #3 from wilson at codesourcery dot com 2010-04-23 22:40 ------- Subject: Re: New: Emit debug info allowing inlined functions to show in stack traces On 04/21/2010 02:26 AM, scovich at gmail dot com wrote: > It would be very nice if gcc emitted debug information that allowed profilers > and debuggers the option to extract a stack trace which included calls to > inlined functions. This would allow developers much greater insight into the > behavior of optimized code. Try the -i option of addr2line. Jim -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43828