From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21239 invoked by alias); 15 Jul 2006 17:27:25 -0000 Received: (qmail 21230 invoked by uid 22791); 15 Jul 2006 17:27:23 -0000 X-Spam-Check-By: sourceware.org Received: from sj-iport-4.cisco.com (HELO sj-iport-4.cisco.com) (171.68.10.86) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 15 Jul 2006 17:27:21 +0000 Received: from sj-dkim-8.cisco.com ([171.68.10.93]) by sj-iport-4.cisco.com with ESMTP; 15 Jul 2006 10:27:20 -0700 X-IronPort-AV: i="4.06,246,1149490800"; d="scan'208"; a="1838915539:sNHT34199296" Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-8.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k6FHRK2r025121; Sat, 15 Jul 2006 10:27:20 -0700 Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id k6FHRK79002277; Sat, 15 Jul 2006 10:27:20 -0700 (PDT) Received: from xmb-sjc-212.amer.cisco.com ([171.70.151.141]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 15 Jul 2006 10:27:19 -0700 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Help: corrupt Stack Date: Sat, 15 Jul 2006 23:12:00 -0000 Message-ID: In-Reply-To: <20060715042015.GC15273@adacore.com> From: "Bizhan Gholikhamseh \(bgholikh\)" To: "Joel Brobecker" Cc: DKIM-Signature: a=rsa-sha1; q=dns; l=1503; t=1152984440; x=1153848440; c=relaxed/relaxed; s=sjdkim8002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=bgholikh@cisco.com; z=From:=22Bizhan=20Gholikhamseh=20\(bgholikh\)=22=20 |Subject:RE=3A=20Help=3A=20corrupt=20Stack; X=v=3Dcisco.com=3B=20h=3DulP74LGf4kt5trSJI2MsxPClz0Y=3D; b=irQwNxJnZpXM/OTYz/iz3XlSnnk86dzMSje1E0m2BOeq+Upp95rNy6xyFWFzjMNu6WfI4YMi S4GvJ6+x436HoQXt22fUudVWoQC4Yv8LaErnQxxaGettvGUf1rHoOf0T; Authentication-Results: sj-dkim-8.cisco.com; header.From=bgholikh@cisco.com; dkim=pass ( sig from cisco.com verified; ); X-IsSubscribed: yes 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/msg00100.txt.bz2 Thanks for reply. , We are using cross compiler for Linux 2.6.11, our host is x86 system and our target system is PPC based. I apologize if this is not enough information, if there is anything else please let me know, however if there are any hints that I should do to help me please let me know. Many thanks in advance, Bizhan -----Original Message----- From: Joel Brobecker [mailto:brobecker@adacore.com]=20 Sent: Friday, July 14, 2006 9:20 PM To: Bizhan Gholikhamseh (bgholikh) Cc: gdb@sourceware.org Subject: Re: Help: corrupt Stack > We are using gdb version 6.3. When we ran gdb on the core dump=20 > 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