Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Xinan Tang" <xinan@TidalNetworks.net>
To: "Fabian Cenedese" <Cenedese@indel.ch>, <gdb@sources.redhat.com>
Subject: RE: View registers from stack frames
Date: Thu, 07 Oct 2004 17:50:00 -0000	[thread overview]
Message-ID: <52BBA75459915749B68F93B604B636CD066711@neptune.TidalNetworks.net> (raw)

Hi 

  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




             reply	other threads:[~2004-10-07 16:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-07 17:50 Xinan Tang [this message]
     [not found] <5.2.0.9.1.20041007134711.01d12d90@NT_SERVER>
     [not found] ` <20041007085738.45b5b55a@saguaro>
2004-10-08 10:14   ` Fabian Cenedese
2004-10-11 19:16     ` Kevin Buettner
2004-10-12 14:03       ` Fabian Cenedese
2004-10-16 15:11         ` Kevin Buettner
  -- strict thread matches above, loose matches on Subject: below --
2004-10-05 12:48 Fabian Cenedese
2004-10-05 13:30 ` Andrew Cagney
2004-10-05 14:02   ` Fabian Cenedese
2004-10-05 14:03     ` Daniel Jacobowitz
2004-10-05 15:00       ` Fabian Cenedese
2004-10-05 17:57         ` Fabian Cenedese
2004-10-06  1:57           ` Andrew Cagney
2004-10-06  7:18             ` Fabian Cenedese
2004-10-06 16:41               ` Kevin Buettner
2004-10-07  9:04                 ` Fabian Cenedese
2004-10-11 19:21                   ` Kevin Buettner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52BBA75459915749B68F93B604B636CD066711@neptune.TidalNetworks.net \
    --to=xinan@tidalnetworks.net \
    --cc=Cenedese@indel.ch \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox