From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16053 invoked by alias); 7 Oct 2004 07:08:56 -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 16037 invoked from network); 7 Oct 2004 07:08:53 -0000 Received: from unknown (HELO smtp.hispeed.ch) (62.2.95.247) by sourceware.org with SMTP; 7 Oct 2004 07:08:53 -0000 Received: from indel.ch (217-162-27-127.dclient.hispeed.ch [217.162.27.127]) by smtp.hispeed.ch (8.12.6/8.12.6/tornado-1.0) with SMTP id i9778ppd005327 for ; Thu, 7 Oct 2004 09:08:51 +0200 Received: from fabi.indel.ch [192.168.1.19] by indel.ch [127.0.0.1] with SMTP (MDaemon.v2.7.SP5.R) for ; Thu, 07 Oct 2004 09:07:26 +0200 Message-Id: <5.2.0.9.1.20041007090225.01d59d40@NT_SERVER> X-Sender: cenedese@NT_SERVER (Unverified) Date: Thu, 07 Oct 2004 09:04:00 -0000 To: gdb@sources.redhat.com From: Fabian Cenedese Subject: Re: View registers from stack frames In-Reply-To: <20041006093816.64f8ac8f@saguaro> 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> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MDaemon-Deliver-To: gdb@sources.redhat.com X-Return-Path: cenedese@indel.ch X-SW-Source: 2004-10/txt/msg00199.txt.bz2 >> 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? Thanks bye Fabi