From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17755 invoked by alias); 6 Feb 2004 19:20:13 -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 17714 invoked from network); 6 Feb 2004 19:20:11 -0000 Received: from unknown (HELO hawaii.kealia.com) (209.3.10.89) by sources.redhat.com with SMTP; 6 Feb 2004 19:20:11 -0000 Received: by hawaii.kealia.com (Postfix, from userid 2049) id B1184D596; Fri, 6 Feb 2004 11:18:55 -0800 (PST) To: gdb Subject: Re: backtrace issues References: From: David Carlton Date: Fri, 06 Feb 2004 19:20:00 -0000 In-Reply-To: (David Carlton's message of "Fri, 06 Feb 2004 10:32:07 -0800") 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/msg00062.txt.bz2 On Fri, 06 Feb 2004 10:32:07 -0800, David Carlton said: > Does GDB have known issues with backtraces on programs compiled with a > recent GCC but with a C library compiled with an old GCC? Actually, the fact that the program was compiled with a recent GCC seems to be irrelevant. I did come up with a stripped-down test case; I've filed PR gdb/1545 about it. David Carlton carlton@kealia.com