From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10687 invoked by alias); 11 Oct 2004 19:03:00 -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 10664 invoked from network); 11 Oct 2004 19:02:57 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 11 Oct 2004 19:02:57 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.10) with ESMTP id i9BJ2qfA031141 for ; Mon, 11 Oct 2004 15:02:57 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i9BJ2lr09874; Mon, 11 Oct 2004 15:02:47 -0400 Received: from localhost.localdomain (vpn50-43.rdu.redhat.com [172.16.50.43]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id i9BJ2kQ7007018; Mon, 11 Oct 2004 15:02:47 -0400 Received: from saguaro (saguaro.lan [192.168.64.2]) by localhost.localdomain (8.12.11/8.12.10) with SMTP id i9BJ2f0I027463; Mon, 11 Oct 2004 12:02:41 -0700 Date: Mon, 11 Oct 2004 19:21:00 -0000 From: Kevin Buettner To: Fabian Cenedese Cc: gdb@sources.redhat.com Subject: Re: View registers from stack frames Message-Id: <20041011120241.12f1b9c0@saguaro> In-Reply-To: <5.2.0.9.1.20041007090225.01d59d40@NT_SERVER> References: <5.2.0.9.1.20041006084237.01cf98c0@NT_SERVER> <5.2.0.9.1.20041005171658.01d208e0@NT_SERVER> <20041005140227.GA13586@nevyn.them.org> <5.2.0.9.1.20041005154532.01d52ec0@NT_SERVER> <5.2.0.9.1.20041005142840.01d03818@NT_SERVER> <5.2.0.9.1.20041005142840.01d03818@NT_SERVER> <5.2.0.9.1.20041005154532.01d52ec0@NT_SERVER> <5.2.0.9.1.20041005171658.01d208e0@NT_SERVER> <5.2.0.9.1.20041006084237.01cf98c0@NT_SERVER> <5.2.0.9.1.20041007090225.01d59d40@NT_SERVER> Organization: Red Hat Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SW-Source: 2004-10/txt/msg00287.txt.bz2 On Thu, 07 Oct 2004 09:08:49 +0200 Fabian Cenedese wrote: > >> The first two frames seem ok, only frame 3 and more are wrong. > >> If more info is needed (e.g. the remote debug protocol) I can also > >> post it here or send to anyone. > >> > >> Well, that only leaves me with the cvs version... > > > >Give the CVS version a try. If that fails too, could you send me > >a test case? > > The cvs version behaves as 6.2 or 6.2.1. I would love to send you a > test case but I don't know how to. I'm working with an embedded > target and some proprietary software. That's why I tried to create > a memory dump and feed this to gdb so I have something I could > send to someone else. But that didn't work out. > > Would it be helpful to have the debug log of the remote protocol > communication? Like that you would see what addresses gdb > probes and the read values. Or maybe a memory dump of the > call stack of a thread? Fabian and I communicated privately on this matter. Fabian determined that it was some custom stack bounds checking code in the prologue which was causing problems with backtraces. We still haven't figured out why this bounds checking code didn't cause earlier versions of GDB problems with its backtraces. Kevin