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

List:       kdevelop-bugs
Subject:    [Bug 143977] New: Stepping in debugger too slow
From:       Thomas McGuire <Thomas.McGuire () gmx ! net>
Date:       2007-04-08 22:20:57
Message-ID: 20070409002056.143977.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=143977         
           Summary: Stepping in debugger too slow
           Product: kdevelop
           Version: unspecified
          Platform: Compiled Sources
        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 (using KDE KDE 3.5.6)
Installed from:    Compiled From Sources
OS:                Linux

The step over function in the debugger is currently too slow to be useful, it takes \
several seconds on my machine. When stepping over, the debugger does the following:

-exec-next
-file-list-exec-source-file
-break-list
-thread-list-ids
-stack-info-depth 6
-stack-list-frames 0 5

I only see -exec-next as necessary.

-file-list-exec-source-file seems to return the current file and line. However this \
is also returned be -exec-next, so why is this needed?

-break-list probably updates the list of breakpoints. Why is this done? Does this \
really need to be done if the breakpoint widget is not shown currently?

-thread-list-ids, -stack-info-depth 6 and -stack-list-frames 0 5 probably update the \
framestack widget. Again, is this also necessary when the framestack widget is not \
shown?


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