Continued a new session after the crash in 321267. Configured the build target and built. Pressed the Debug button, and was transported to the Debug view and then back to the code browser. Thinking that it was the testcase finishing immediately, I opened one of the files and set a breakpoint. Pressed the Debug button again, and was again transported tot he Debug view and then back to the code browser. Clicked the button once or twice more, and KDevelop crashed. Dr. Konki refuses to report the stack trace as it thinks it is incomplete. Looking at the traces, there's an LWP 7782 with a very suspicious-looking stack whose symbols cannot be resolved (addresses include 0x60 and 0x8a). Could it be a corrupt stack? I'll attempt to attach the stacktrace after filing the bug. Reproducible: Always
Created attachment 80582 [details] Stack trace, including suspicious-looking thread
You most likely have a problem with your binaries. Can you maybe try upgrading to kdevelop 4.5.2?
I have the binaries that come with Ubuntu 13.04, and I've verified with debsums that they are not modified. If the Ubuntu binaries are broken, then this is a huge issue.
Here you have the information on how to use the latest stable version: http://userbase.kde.org/KDevelop/Install4.5#Kubuntu
Sorry, not really interested in installing it manually. What's wrong with the binaries packaged with Ubuntu 13.04?
What version of Qt do you have installed? Is it Qt 4.8.5? The crash looks like a typical crash in JIT, i.e. QtScript/QML/QtWebKit related. Qt 4.8.5 fixed two more crashes there so please ensure you update.
All versions are what were the latest in Ubuntu 13.04 release at the time the report was filed. The list of current versions can be found via http://packages.ubuntu.com/raring/kdevelop (which lists version "4:4.8.4+dfsg-0ubuntu9" for the package "libqtcore4"), but I think some of them have been updated since the report was filed.
OK, then wait for the Ubuntu people to provide you with an updated Qt package. Note: In the future, please add such informations to reports you create. Many of us don't use Ubuntu nor do we want to have to correlate report dates with package versions.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!