From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10643 invoked by alias); 14 Jun 2005 21:26:55 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 10268 invoked by uid 22791); 14 Jun 2005 21:26:43 -0000 Received: from mail-out4.apple.com (HELO mail-out4.apple.com) (17.254.13.23) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 14 Jun 2005 21:26:43 +0000 Received: from mailgate1.apple.com (a17-128-100-225.apple.com [17.128.100.225]) by mail-out4.apple.com (8.12.11/8.12.11) with ESMTP id j5ELQfd6011951 for ; Tue, 14 Jun 2005 14:26:41 -0700 (PDT) Received: from relay3.apple.com (relay3.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.3.17) with ESMTP id for ; Tue, 14 Jun 2005 14:26:41 -0700 Received: from [17.201.22.21] (moleja.apple.com [17.201.22.21]) by relay3.apple.com (8.12.11/8.12.11) with ESMTP id j5ELQfV1027951 for ; Tue, 14 Jun 2005 14:26:41 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v728) In-Reply-To: <20050614205212.GK62467@keyslapper.net> References: <20050614014520.GG24814@keyslapper.net> <20050614020138.GA19453@nevyn.them.org> <20050614033256.GB48802@keyslapper.net> <10DBEAA7-48B2-4298-A8CC-58A138415516@apple.com> <20050614205212.GK62467@keyslapper.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <763A9227-0BD8-45EE-A30E-0992464739AD@apple.com> Content-Transfer-Encoding: 7bit From: Jason Molenda Subject: Re: stack corruption? Date: Tue, 14 Jun 2005 21:26:00 -0000 To: gdb@sources.redhat.com X-SW-Source: 2005-06/txt/msg00145.txt.bz2 On Jun 14, 2005, at 1:52 PM, Louis LeBlanc wrote: > Basically, I'm not entirely sure. The codebase in question has never > had this problem in the past, but now (with a newer version of gdb, > and after much work on my code) I always get the corrupt stack notice > when I open the process in gdb. You mean you're doing a backtrace and mid-way through you get an error message like Previous frame identical to this frame (corrupt stack?) and the backtrace stops at that point? These days, the majority of the time, this is gdb getting confused. Your program don't necessarily have a corrupt stack. > The gdb version I am using is: > $ gdb -v > GNU gdb 6.3.0.20050516-cvs > > I have been planning to get a later snapshot, but haven't gotten > around to it yet. In addition, I'd recommend grabbing an older gdb and give that a try, like 6.0. There was some work done in the frame handling code that changed the way stack backtraces are done, and it gives up too easily. I don't remember when the new frame code went in, but gdb-6.0 is probably early enough. Downloading & building gdb doesn't take much time; it's worth doing this as a sanity check. Jason