public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "rmoseley at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/4223] New: Source window slowness
Date: Tue, 20 Mar 2007 19:19:00 -0000	[thread overview]
Message-ID: <20070320191925.4223.rmoseley@redhat.com> (raw)

While fixing bz #4157 I downloaded the gnome-utils package so I could use the
"gcalctool" to use as an example of an rpm package that was downloaded, built
and then try to debug it.  In the process of debugging I noticed some slowness
in the loading of source files when stack frames are clicked on.  Especially
stack frame #7(gtk.c line #492).  (BTW, I was using gnome-utils-2.14.0-3.src.rpm
for the test so this could change with other versions.)

When clicking on the gtk.c stack frame it takes over 20 seconds on my i686/2GHz
P4 machine to bring up that window.  The source file for that has 3432 lines of
code in the current incarnation of that file.  I'm not sure right now where the
time is being spent.

-- 
           Summary: Source window slowness
           Product: frysk
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: frysk-bugzilla at sourceware dot org
        ReportedBy: rmoseley at redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=4223

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


             reply	other threads:[~2007-03-20 19:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-20 19:19 rmoseley at redhat dot com [this message]
2007-03-20 19:24 ` [Bug general/4223] " rmoseley at redhat dot com
2007-03-20 20:23 ` rmoseley at redhat dot com
2007-03-23 12:46 ` mcvet at redhat dot com

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=20070320191925.4223.rmoseley@redhat.com \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=frysk-bugzilla@sourceware.org \
    /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).