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

List:       kdevelop-bugs
Subject:    [Bug 102319] New: Infinite recursion leads to a very long delay to display stack and makes impossibl
From:       kdevelop-bugs-admin () barney ! cs ! uni-potsdam ! de
Date:       2005-03-23 21:37:50
Message-ID: 20050323223747.102319.Benjamin.Piwowarski () lip6 ! fr
[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=102319         
           Summary: Infinite recursion leads to a very long delay to display
                    stack and makes impossible another debugging if stopped
           Product: kdevelop
           Version: unspecified
          Platform: Debian testing
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: Benjamin.Piwowarski lip6 fr


Version:            (using KDE KDE 3.3.2)
Installed from:    Debian testing/unstable Packages

When debugging after a crash due to an infinite loop, like eg

void f() { f(); }
int main(int, char **) { f(); }

it takes a lot of time (and memory) to display the stack, if it is ever possible. \
Would it be possible to display only a part of the stack?

Moreover, when one stops the debugger before the stack is displayed the memory \
doesn't seem to be freed (and keep on growing). It is also impossible to start a new \
debugging process.


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