public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Roland Schwingel <roland@schwingel.com>
To: gdb <gdb@sources.redhat.com>
Subject: gdb/Insight 5.3 really slow when stepping
Date: Wed, 21 May 2003 12:43:00 -0000	[thread overview]
Message-ID: <3ECB7402.7040508@schwingel.com> (raw)

Hi....

I am using gdb/insight 5.3 on windows (cygwin). And it is *really* slow when stepping...

So I started out to detect where it is slow. Even on stupid lines eg. stepping
thru this block (snipped out of Insight)

- 2370 int	numLines = 0;
   2371 NSArray	*predefinedNames;
- 2372 BOOL	mustGenNames = NO;

On every step gdb/insight is doing (in my case) about 17800 (!) filesystem accesses.
I used FileMon from SysInternals. Obviously it checks presence of the source file
and a huge number of headers and other source files. Both system header and selfmade onces.

This makes stepping *really* slow. I encountered that it depends on the file you are
stepping thru in how slow it is.

Is this checking necessary all the time (on every step)? Wouldn't it be enough to scan
all these things just once when entering the file the first time? Can it be switched off?

Thanks for your help,

Roland

                 reply	other threads:[~2003-05-21 12:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3ECB7402.7040508@schwingel.com \
    --to=roland@schwingel.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).