[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-bugs
Subject: [Bug 144254] New: Local variable tree expanded unnecessarily,
From: Thomas McGuire <Thomas.McGuire () gmx ! net>
Date: 2007-04-15 12:53:23
Message-ID: 20070415145322.144254.Thomas.McGuire () gmx ! net
[Download RAW message or body]
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=144254
Summary: Local variable tree expanded unnecessarily, slowing down
frame switching
Product: kdevelop
Version: unspecified
Platform: Ubuntu Packages
OS/Version: Linux
Status: NEW
Severity: normal
Priority: NOR
Component: CPP Debugger
AssignedTo: kdevelop-bugs kdevelop org
ReportedBy: Thomas.McGuire gmx net
Version: 3.4 SVN (3.5 branch) (using KDE KDE 3.5.6)
Installed from: Ubuntu Packages
OS: Linux
For big projects, updating the local variables takes ages (several seconds) because a \
lot of GDB commands (-var-update*, -var-evaluate-expression, whatis, print) are \
executed.
Fortunately, collapsing the "Locals" tree prevents updates.
However, the "Locals" tree is expanded again when changing frames using the \
framestack widget. This should not happen. Because of this, using the framestack \
widget for switching frames is unusable for big projects.
When switching frames, the "Locals" tree should not be automatically expanded.
The cause for this is the call "frame->setOpen(true)" in \
VariableTree::demand_frame_root. However, this can not be solved by simply removing \
this call, since in demand_frame_root, a new "Local" tree is created, which is only \
removed later in VariableTree::frameIdReady. Removing the setOpen() call would also \
prevent frameIdReady() to be called.
I do not know how to solve this properly myself.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic