[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 146164] avoid gdb instructions if variable panel not visible
From:       Andreas Pakulat <apaku () gmx ! de>
Date:       2007-05-30 16:37:01
Message-ID: 20070530163701.3592.qmail () ktown ! kde ! org
[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=146164         




------- Additional Comments From apaku gmx de  2007-05-30 18:37 -------
You can see the full gdb output by right-clicking the gdb tab and selecting show \
internal commands.

Yes when you click an item in the framestack the debugger does something like "go to \
that point", which also reloads the variable list (and opens the file and positions \
the cursor there). I think the stuff that KDevelop does are pretty much the same as \
when stepping, except that it needs to find a file. So if the file is outside the \
project that will take quite some time.


[prev in list] [next in list] [prev in thread] [next in thread]