From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20713 invoked by alias); 6 Feb 2004 18:32:08 -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 20698 invoked from network); 6 Feb 2004 18:32:07 -0000 Received: from unknown (HELO hawaii.kealia.com) (209.3.10.89) by sources.redhat.com with SMTP; 6 Feb 2004 18:32:07 -0000 Received: by hawaii.kealia.com (Postfix, from userid 2049) id 5AFD3D35F; Fri, 6 Feb 2004 10:32:07 -0800 (PST) To: gdb Subject: backtrace issues From: David Carlton Date: Fri, 06 Feb 2004 18:32:00 -0000 Message-ID: User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Reasonable Discussion, linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2004-02/txt/msg00061.txt.bz2 Does GDB have known issues with backtraces on programs compiled with a recent GCC but with a C library compiled with an old GCC? It happens not infrequently around here that we get backtraces that GDB 5.3 can read but where mainline GDB can't get past the first few frames. I know I've seen this in the following situation (user code is compiled with GCC 3.2, system libraries are from Red Hat 7.3): * We have user code, which seg faults. * Our signal handler gets called. This signal handler then prints out a (useful) backtrace, using the functions provided by the C library. It then calls abort(). * A core file is generated. Then, when we try to read the core file, mainline GDB gets confused a few frames down (right around the signal handler), while GDB 5.3 has no problem with the core file. Is this a known issue? Is there anything useful I can do to help diagnose the issue? Obviously I'll try to produce a stripped-down example where this happens, but if I'm not able to do so, I can certainly run GDB on itself to see what's going on, if anybody can point me to useful places to look at. David Carlton carlton@kealia.com