From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10353 invoked by alias); 7 Oct 2003 16:23:47 -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 10346 invoked from network); 7 Oct 2003 16:23:46 -0000 Received: from unknown (HELO srv01.cas.org) (134.243.50.9) by sources.redhat.com with SMTP; 7 Oct 2003 16:23:46 -0000 Received: from cas.org (pmd24awu [134.243.216.44]) by srv01.cas.org (8.12.9/8.12.9/CAS_MAIL_HUB-3.02) with ESMTP id h97GNhL0013100 for ; Tue, 7 Oct 2003 12:23:44 -0400 (EDT) Message-ID: <3F82E88E.3090300@cas.org> Date: Tue, 07 Oct 2003 16:23:00 -0000 From: Paul Dubuc Organization: Chemical Abstracts Service (CAS) User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: GDB Mailing List Subject: GDB 6.0 backtrace only prints 4 stack frames Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-10/txt/msg00119.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? -- Paul M. Dubuc mailto:pdubuc@cas.org Room 4349B (614) 447-3600 x2692 http://www.purl.org/dubuc/cas/