From: Keith Seitz <kseitz@firetalk.com>
To: Leon Pollak <leonp@plris.com>
Cc: James Ingham <jingham@cygnus.com>, insight@sourceware.cygnus.com
Subject: Re: How to block local variables?
Date: Tue, 25 Apr 2000 05:26:00 -0000 [thread overview]
Message-ID: <39058EB3.71AF9429@firetalk.com> (raw)
In-Reply-To: <4.3.0.20000425092503.00a94f00@plris.com>
Leon Pollak wrote:
>
> At 11:29 24/04/00 -0700, you wrote:
> >Leon,
> >
> >You are right about how Insight updates local variables. The only
> >way to stop this is to close the local variables window. You can use
> >the Watch window to selectively watch particular variables instead.
> Jim, please, excuse me to return to this, but the window was
> closed and all my experiments show (I know that this may be incorrect, but
> still...) that the window is updated (or the corresponding data is
> retrieved?) even been closed. May it be?
> Once more, excuses.
Um, I don't think so. GDB does, however, update the register cache every
time the inferior's state changes. To see how much data is flying around
over a remote connection, use the remotedebug or remotelog variables:
these will show you exactly what's going on at the protocol level
(provided your target uses gdb's remote protocol).
Keith
--
Why chat when you can Firetalk?
Firetalk ID: Keith (10320)
www.firetalk.com
next prev parent reply other threads:[~2000-04-25 5:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-24 3:34 Leon Pollak
2000-04-24 11:26 ` James Ingham
2000-04-25 0:26 ` Leon Pollak
2000-04-25 5:26 ` Keith Seitz [this message]
2000-04-25 7:23 ` Fernando Nasser
2000-04-25 10:13 ` James Ingham
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=39058EB3.71AF9429@firetalk.com \
--to=kseitz@firetalk.com \
--cc=insight@sourceware.cygnus.com \
--cc=jingham@cygnus.com \
--cc=leonp@plris.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).