Summary: | KDevelop reproducely crashes when typed text [KDevelop::Declaration::abstractType] | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | alecn2002 |
Component: | Language Support: CPP (old) | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | aleixpol, andre.stein.1985, cmazarine, niko.sams, zarzych |
Priority: | NOR | ||
Version: | 4.2.2 | ||
Target Milestone: | 4.2.3 | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | KDevelop Crash on pressing <Enter> inside h file |
Description
alecn2002
2011-09-21 14:30:52 UTC
I've tried to reproduce the crash but I can't. Could you post a simple test case that crashes your kdevelop? Created attachment 73420 [details]
KDevelop Crash on pressing <Enter> inside h file
Crash report
KDevelop often crashes while developing (writing in header or source files (h or cpp)) I suspect that is related to intellisense but I'm not 100% sure. I'm still trying to find a way to always reproduce the crashes. There is no special word or character I type prior to crash (at least until now I didn't noticed crashes to be triggered by a special word/character). The frequency of crashes is between few minutes or 2 hours, I've always got a crash in less than 2 hours of working with KDevelop. Also question related to the dump report. There are some question marks in that file like: #7 0x0000000000000000 in ?? () I don't know how to find the dbg symbols for these lines and the crash report generator doesn't allow the report to be sent while there are question marks in report. Do you have any hint on solving this? cristi, your crash is not related to this bug. I suspect 297661 is your issue (QtScript is used in indentation scripts when pressing Enter). I still have crashes when typing text in C++ source files (Sometimes when typing in comments, sometimes if a open a new namespace/class scope). I have a recent KDE version so the mentioned bug can't be the cause.. I'll to find something reproducible. *** This bug has been marked as a duplicate of bug 273707 *** |