From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13772 invoked by alias); 11 Dec 2007 20:59:45 -0000 Received: (qmail 13763 invoked by uid 22791); 11 Dec 2007 20:59:45 -0000 X-Spam-Check-By: sourceware.org Received: from rv-out-0910.google.com (HELO rv-out-0910.google.com) (209.85.198.187) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 11 Dec 2007 20:59:36 +0000 Received: by rv-out-0910.google.com with SMTP id l15so2078579rvb for ; Tue, 11 Dec 2007 12:59:33 -0800 (PST) Received: by 10.140.180.13 with SMTP id c13mr5297554rvf.1197406773420; Tue, 11 Dec 2007 12:59:33 -0800 (PST) Received: by 10.141.34.11 with HTTP; Tue, 11 Dec 2007 12:59:33 -0800 (PST) Message-ID: Date: Tue, 11 Dec 2007 20:59:00 -0000 From: "Ananth Sowda" To: gdb@sourceware.org Subject: Call stack trace implementation MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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/msg00078.txt.bz2 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? Thanks