public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <kseitz@firetalk.com>
To: Paul_Heijman@eu.omron.com
Cc: insight@sourceware.cygnus.com
Subject: Re: Performance question
Date: Wed, 12 Jul 2000 06:00:00 -0000	[thread overview]
Message-ID: <396C6C00.1D50EF50@firetalk.com> (raw)
In-Reply-To: <4125691A.003F2FCB.00@eu.omron.com>

Paul_Heijman@eu.omron.com wrote:
> 
> hi there,
> 
> when I'm debugging with Insight and if I want to look at a certain structure or
> array, it seems like if GDB (or Insight) retrieves each array element from the
> target SEPERATELY. It looks like GDB (or Insight) inserts a delay of approx. 3/4
> second between each element it receives. This makes watching these kinds of
> structs very slow. For instance, an array of 10 integers takes GDB almost 8
> seconds.
> 
> Can someone confirm GDB puts in a explicit delay? And, if so, is there a way to
> shorten this?

I've never noticed such a thing. You might try turning on a remote log
file and seeing what is happening (turn it on before "opening" the array
but AFTER you're attached and running). See "help set remotelogfile". If
you keep the console window open, are there any messages attached?

I cannot imagine that this has anything to do with Insight proper, since
one of the testcases I used included linked lists with >512 element
arrays, and I could still step through these on a native machine without
any noticeable degradation of speed. But, GUIs are very complex, and
anything is possible. :-O

(Can you remind me, what does "gdb -v" or "show version" show again?)
Keith

      reply	other threads:[~2000-07-12  6:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-12  3:32 Paul_Heijman
2000-07-12  6:00 ` Keith Seitz [this message]

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=396C6C00.1D50EF50@firetalk.com \
    --to=kseitz@firetalk.com \
    --cc=Paul_Heijman@eu.omron.com \
    --cc=insight@sourceware.cygnus.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).