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

List:       kdevelop-bugs
Subject:    [Bug 147607] CPP debugger is very slow on steps
From:       Anderson Luiz da Silva <andyluiz () yahoo ! com>
Date:       2008-07-02 0:38:39
Message-ID: 20080702003839.24560.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=147607         




------- Additional Comments From andyluiz yahoo com  2008-07-02 02:38 -------
I agree that if one executes the same commands by hand the debugger will take the \
same time to respond but when debugging direct in gdb I don't need to see neither all \
threads nor the stack after each step. And when I do need to see them I don't bother \
to wait a bit. So gdb is slow but I disagree that calling -thread-select for every \
thread is necessary when the frame stack window is not visible.

I've been using a modified version of KDevelop that only lists threads and stack when \
the Frame Stack window becomes (or is) visible and it works very well and very \
faster.

Remember that I'm using an application that has hundreds of threads. Debugging an \
application with only one or a couple of threads makes the slowness almost \
imperceptible.

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs


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