From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14051 invoked by alias); 8 Oct 2003 17:27:44 -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 14007 invoked from network); 8 Oct 2003 17:27:42 -0000 Received: from unknown (HELO babbler.bmc.com) (198.207.223.240) by sources.redhat.com with SMTP; 8 Oct 2003 17:27:42 -0000 Received: from ec03-hou.bmc.com (localhost [127.0.0.1]) by babbler.bmc.com (8.10.2-BMC/8.10.2) with ESMTP id h98HSav08118 for ; Wed, 8 Oct 2003 12:28:36 -0500 (CDT) Received: by ec03-hou.bmc.com with Internet Mail Service (5.5.2653.19) id ; Wed, 8 Oct 2003 12:27:39 -0500 Message-ID: From: "Dana, Eric" To: "'gdb@sources.redhat.com'" Subject: Re: GDB 6.0 backtrace only prints 4 stack frames Date: Wed, 08 Oct 2003 17:27:00 -0000 MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2003-10/txt/msg00138.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.