From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21594 invoked by alias); 8 Oct 2003 17:59:35 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 21583 invoked from network); 8 Oct 2003 17:59:34 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 8 Oct 2003 17:59:34 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 439262B89; Wed, 8 Oct 2003 13:59:33 -0400 (EDT) Message-ID: <3F845085.8070007@redhat.com> Date: Wed, 08 Oct 2003 17:59:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Dana, Eric" Cc: "'gdb@sources.redhat.com'" Subject: Re: GDB 6.0 backtrace only prints 4 stack frames References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-10/txt/msg00140.txt.bz2 > I've just downloaded GDB 6.0 and built it for Solaris 2.8. When examining >>a core from a program (compiled with GNU g++ 2.95.3), the "backtrace" (or >>"where") command only prints stack frames 0-3 for each thread. Passing a >>number larger than 4 to the command makes no difference. This isn't a >>problem with gdb 5.3. Is this a known bug? > > > We have been experiencing the same problem on Solaris 2.8 32-bit while > debugging > a shared library. > > Eric Dana > BMC Software Inc. Likely this: > mips*-*-* > powerpc*-*-* > sparc*-*-* > > GDB's SPARC, MIPS and PowerPC targets, in 6.0, have not been updated > to use the new frame mechanism. > > People encountering problems with these targets should consult GDB's > web pages and mailing lists (http://www.gnu.org/software/gdb/) to see > if there is an update. from the PROBLEMS file. There's a new sparc branch to help people work on it in the mainline. Andrew