Summary: | Crash while debugging with watch/variable view | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | lament |
Component: | general | Assignee: | KDevelop Developers <kdevelop-devel> |
Status: | RESOLVED FIXED | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | RedHat Enterprise Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
lament
2003-04-30 02:51:07 UTC
I don't understand the debugger code well enough to understand this, but I can reproduce it: Debug gideon -> set a breakpoint at line 81 of parts/closer/closer_part.cpp in the current souce (the line is "void CloserPart::closeFiles( QStringList const & fileList )" - the method head). Trigger this code (assumes closerpart is loaded) by hitting ctrl+alt-W and clicking "ok". When the debugger stops the program at line 81, expand the stackframe in the variables/watch window -> CRASH, with the reported backtrace. Putting the breakpoint inside the method (line 83) produces no such crash on expansion of the stackframe. For me, this happens everytime. I first noticed it somewhere else, so I don't think it's that particular to the code being debugged, but this was an easy place to trigger it. Hopefully fixed in CVS. I committed a patch that handles the problem for my case (see previous comment) and since it was the same stacktrace, maybe it helps. Please reopen if the patch is unsuccessful. |