Summary: | kdevelop crash when starting a project build | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Bernie Clarke <bclarke> |
Component: | general | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | CC: | olivier.jg |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | 4.2.0 | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Bernie Clarke
2011-05-27 16:54:15 UTC
This is a really strange-looking bug. Look at part 8: #8 0x04920eae in QObject::connect (sender=0x8870760, signal=0x88a7352 "loseEditor(QWidget*,QAbstractItemDelegate::EndEditHint)", receiver=0xa7b37d0, method=0x595e648 "1closeEditor(QWidget*,QAbstractItemDelegate::EndEditHint)", type=Qt::AutoConnection) at kernel/qobject.cpp:2508 The signal is "loseEditor"? The SIGNAL() macro would normally prepend a 2 to the name also. Maybe that's normal, but taken together I'd say there's perhaps binary incompatibility, or maybe a problem with Qt? Is your version of KDevelop compiled against your version of Qt? |