From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4235 invoked by alias); 7 Oct 2004 16:45:31 -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 4206 invoked from network); 7 Oct 2004 16:45:27 -0000 Received: from unknown (HELO neptune.TidalNetworks.net) (67.114.153.34) by sourceware.org with SMTP; 7 Oct 2004 16:45:27 -0000 Content-class: urn:content-classes:message Subject: RE: View registers from stack frames MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 07 Oct 2004 17:50:00 -0000 Message-ID: <52BBA75459915749B68F93B604B636CD066711@neptune.TidalNetworks.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Xinan Tang" To: "Fabian Cenedese" , X-SW-Source: 2004-10/txt/msg00224.txt.bz2 Hi=20 This can be done by issuing these two commands: >set debug remote 1 >set remotelogfile file_xyz Then file_xyz will record everything including the remote protocol packets. Good luck --Xinan -----Original Message----- From: gdb-owner@sources.redhat.com [mailto:gdb-owner@sources.redhat.com] On Behalf Of Fabian Cenedese Sent: Thursday, October 07, 2004 12:09 AM To: gdb@sources.redhat.com Subject: Re: View registers from stack frames 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