Summary: | crash in problem reported on null pointer deref | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Milian Wolff <mail> |
Component: | Problem reporter | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | bellamy.beau, dimsuz, mad.f3ka |
Priority: | NOR | ||
Version First Reported In: | git master | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Milian Wolff
2009-09-11 16:14:41 UTC
I'd want to introduce an additional check here, like in the dtor of the problem reporter. But looking at the ctor and it's Q_ASSERT(m_document) I wasn't sure. Hence this bugreport. I think we have another incarnation of this somewhere else. The problem here is that the nested event loop from the context menu processes events that shouldn't be processed and hence triggers the problemreporter. I don't know about more details, but one way to "fix" this would be just show()'ing the context menu (and connecting its hidden() signal to its deleteLater() slot) instead of exec()'ing it. *** Bug 211596 has been marked as a duplicate of this bug. *** *** Bug 213136 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 195047 *** *** Bug 219158 has been marked as a duplicate of this bug. *** |