From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14843 invoked by alias); 11 Dec 2007 21:01:39 -0000 Received: (qmail 14835 invoked by uid 22791); 11 Dec 2007 21:01:39 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 11 Dec 2007 21:01:30 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 662F798020; Tue, 11 Dec 2007 21:01:28 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 511B39801F; Tue, 11 Dec 2007 21:01:28 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.68) (envelope-from ) id 1J2CEJ-0004w5-Ar; Tue, 11 Dec 2007 16:01:27 -0500 Date: Tue, 11 Dec 2007 21:01:00 -0000 From: Daniel Jacobowitz To: Ananth Sowda Cc: gdb@sourceware.org Subject: Re: Call stack trace implementation Message-ID: <20071211210127.GA18958@caradoc.them.org> Mail-Followup-To: Ananth Sowda , gdb@sourceware.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.15 (2007-04-09) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-12/txt/msg00079.txt.bz2 On Tue, Dec 11, 2007 at 12:59:33PM -0800, Ananth Sowda wrote: > My question is on implementation of stack backtrace on architures, > MIPS and PPC. Is the implementation based on libunwind and unwind > directives in the executable? Or is it based on older code which > analyzes prologue of a function? Or a mix of both approaches? Both prologue analysis and call frame information. Libunwind is not used except on IA64; GDB has its own support for DWARF-2 unwind tables. -- Daniel Jacobowitz CodeSourcery