From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-31282-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 21365 invoked by alias); 5 Mar 2008 17:26:36 -0000
Received: (qmail 21349 invoked by uid 22791); 5 Mar 2008 17:26:35 -0000
X-Spam-Check-By: sourceware.org
Received: from qnxmail.qnx.com (HELO qnxmail.qnx.com) (209.226.137.76)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 05 Mar 2008 17:26:16 +0000
Received: from smtp.ott.qnx.com (smtp.ott.qnx.com [10.42.96.5]) 	by hub.ott.qnx.com (8.9.3/8.9.3) with ESMTP id MAA02159; 	Wed, 5 Mar 2008 12:08:30 -0500
Received: from [10.42.100.129] (dhcp-100-129 [10.42.100.129]) by smtp.ott.qnx.com (8.8.8/8.6.12) with ESMTP id MAA16112; Wed, 5 Mar 2008 12:26:09 -0500
Message-ID: <47CED7B1.2050205@qnx.com>
Date: Wed, 05 Mar 2008 18:08:00 -0000
From: Aleksandar Ristovski <aristovski@qnx.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Joel Brobecker <brobecker@adacore.com>
CC: Guillaume MENANT <guillaume.menant@geensys.com>, gdb@sourceware.org
Subject: Re: Previous frame identical to this frame (corrupt stack?)
References: <15854428.post@talk.nabble.com> <20080305171516.GA3894@adacore.com>
In-Reply-To: <20080305171516.GA3894@adacore.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: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2008-03/txt/msg00052.txt.bz2

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.

> 
> 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.
>