Summary: | KDevelop Crash | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Steven Sroka <Sroka.Steven> |
Component: | general | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED UPSTREAM | ||
Severity: | crash | CC: | casaobscura, Sroka.Steven |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | 4.1.0 | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Steven Sroka
2010-10-07 02:25:01 UTC
looks like a Qt bug to me. Maybe you could run kdevelop through valgrind if you can reproduce the crash. Or give us a way to reproduce it. Otherwise nothing we can do about it. It might be a KDevelop bug. I'm hoping that if it is, that it was fixed in KDevelop 4.1. There was a bug fixed regarding an innocent crash in KDevelop: "Fixed a common crash on shutdown (which never resulted in data losses but was very annoying)" - http://dot.kde.org/2010/10/26/kdevelop-41-brings-git-integration If it's a Qt bug, then I have to wait until Qt 4.7 becomes stable on my OS. it's definitely not the bug I mentioned in the release announcement. so if you ever come around to get a valgrind report then send it to us. thanks *** Bug 308069 has been marked as a duplicate of this bug. *** Upstream bug, likely. |