From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25166 invoked by alias); 5 Mar 2008 18:08:54 -0000 Received: (qmail 25156 invoked by uid 22791); 5 Mar 2008 18:08:53 -0000 X-Spam-Check-By: sourceware.org Received: from s200bog12.obsmtp.com (HELO s200bog12.obsmtp.com) (207.126.150.126) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 05 Mar 2008 18:08:26 +0000 Received: from source ([164.129.1.35]) (using TLSv1) by eu2sys200bob012.postini.com ([207.126.147.11]) with SMTP; Wed, 05 Mar 2008 18:07:50 UTC Received: from zeta.dmz-eu.st.com (ns2.st.com [164.129.230.9]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 109D3DB65; Wed, 5 Mar 2008 18:07:49 +0000 (GMT) Received: from mail1.bri.st.com (mail1.bri.st.com [164.129.8.218]) by zeta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 067A94C0F3; Wed, 5 Mar 2008 18:07:47 +0000 (GMT) Received: from [164.129.12.194] (bri0669.bri.st.com [164.129.12.194]) by mail1.bri.st.com (MOS 3.7.5a-GA) with ESMTP id CJU88078 (AUTH stubbsa); Wed, 5 Mar 2008 18:07:46 GMT Message-ID: <47CEE170.8060802@st.com> Date: Wed, 05 Mar 2008 19:52:00 -0000 From: Andrew STUBBS User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: Aleksandar Ristovski Cc: Joel Brobecker , Guillaume MENANT , gdb@sourceware.org Subject: Re: Previous frame identical to this frame (corrupt stack?) References: <15854428.post@talk.nabble.com> <20080305171516.GA3894@adacore.com> <47CED7B1.2050205@qnx.com> In-Reply-To: <47CED7B1.2050205@qnx.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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/msg00053.txt.bz2 Aleksandar Ristovski wrote: > Joel Brobecker wrote: >>> 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 might also be experiencing a library mismatch. Or it might just have run out of stack frames, but has no way to tell. I'm not sure what the current behaviour is, but at least one past version of GDB gives this message in this case.