From: James Ingham <jingham@cygnus.com>
To: leonp@plris.com
Cc: Insight <insight@sourceware.cygnus.com>
Subject: Re: How to block local variables?
Date: Mon, 24 Apr 2000 11:26:00 -0000 [thread overview]
Message-ID: <14596.37513.342243.743047@leda.cygnus.com> (raw)
In-Reply-To: <390415A2.E05EC472@plris.com>
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
> Hello,
> I use Insight with remote "serial" target and therefore the data
> "extraction" from it is not very fast.
> I noticed that if the routine I am stepping through has rather big
> amount of local vars the "step time" is long.
> Is my hypothesis, that on each step all local variables are renewed
> is correct?
> And if yes, how can this be blocked?
> Many thanks for possible help.
> leonp@plris.com
>
>
>
next prev parent reply other threads:[~2000-04-24 11: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 [this message]
2000-04-25 0:26 ` Leon Pollak
2000-04-25 5:26 ` Keith Seitz
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=14596.37513.342243.743047@leda.cygnus.com \
--to=jingham@cygnus.com \
--cc=insight@sourceware.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).