From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8153 invoked by alias); 15 Jul 2006 04:20:21 -0000 Received: (qmail 8145 invoked by uid 22791); 15 Jul 2006 04:20:21 -0000 X-Spam-Check-By: sourceware.org Received: from nile.gnat.com (HELO nile.gnat.com) (205.232.38.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 15 Jul 2006 04:20:19 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id 5F58D48CDD9; Sat, 15 Jul 2006 00:20:17 -0400 (EDT) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 20315-01-6; Sat, 15 Jul 2006 00:20:17 -0400 (EDT) Received: from takamaka.act-europe.fr (unknown [70.71.0.212]) by nile.gnat.com (Postfix) with ESMTP id 0031048CDD2; Sat, 15 Jul 2006 00:20:16 -0400 (EDT) Received: by takamaka.act-europe.fr (Postfix, from userid 507) id AFB7E47EFA; Fri, 14 Jul 2006 21:20:15 -0700 (PDT) Date: Sat, 15 Jul 2006 06:38:00 -0000 From: Joel Brobecker To: "Bizhan Gholikhamseh (bgholikh)" Cc: gdb@sourceware.org Subject: Re: Help: corrupt Stack Message-ID: <20060715042015.GC15273@adacore.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-07/txt/msg00095.txt.bz2 > We are using gdb version 6.3. When we ran gdb on the core dump > generated, it complains with following messages: > "Previous frame identical to this frame (corrupt stack?)" > Is this a known bug, is there a work around or patch > available? I am afraid you are not providing enough information for anyone to help you here. 6.3 is pretty old at this point, so you should try 6.5. Also, with core files, I have noticed that people sometimes analyze them on a machine that's different from the one where the core file was generated. Is this the case for you? If it is, chances are the system libraries are slightly different, and that will cause trouble during the backtrace computation. Otherwise, you will probably need to specify at least the platform on which you are running, but even then, I doubt that this will be sufficient to help you. You probably need to provide a way for us to reproduce your problem. -- Joel