From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15689 invoked by alias); 5 Mar 2008 17:15:39 -0000 Received: (qmail 15643 invoked by uid 22791); 5 Mar 2008 17:15:38 -0000 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 05 Mar 2008 17:15:20 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id F21E12AAB4A; Wed, 5 Mar 2008 12:15:18 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id f5aNkIe9Zje4; Wed, 5 Mar 2008 12:15:18 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id B9D6C2AAB01; Wed, 5 Mar 2008 12:15:18 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 87D95E7ACB; Wed, 5 Mar 2008 09:15:16 -0800 (PST) Date: Wed, 05 Mar 2008 17:26:00 -0000 From: Joel Brobecker To: Guillaume MENANT Cc: gdb@sourceware.org Subject: Re: Previous frame identical to this frame (corrupt stack?) Message-ID: <20080305171516.GA3894@adacore.com> References: <15854428.post@talk.nabble.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15854428.post@talk.nabble.com> User-Agent: Mutt/1.4.2.2i Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-03/txt/msg00051.txt.bz2 > What does it means ? What have I to look at in order to check if I have an > mistake in my program ? You really didn't provide much information (either GDB version, platform, etc). But it could be either: - a corrupt call-stack, or maybe corrupt debugging info (frame info) - a bug in GDB You can try using GDB from CVS head to see if you have better results. Otherwise, you will need to inspect the frame where the backtrace stops, and verify that it is not screwed. You might also have to check the frame info data if your executable has them. -- Joel