| Summary: | kdevelop crashes on closing | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Patrick Spendrin <ps_ml> |
| Component: | general | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | kde-windows |
| Priority: | NOR | ||
| Version: | git master | ||
| Target Milestone: | 4.2.3 | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Patrick Spendrin
2011-07-03 20:27:19 UTC
does this also happen in Kate? It doesn't really look like KDevelop specific to me... If not then I'll have to look for scripts/commands being added in KDevelop... no, it doesn't happen with kate. here is the tail of the debug output: [4720] kdevelop(4720)/kdevplatform (shell) __thiscall KDevelop::Core::~Core(void): [4720] kdevelop(4720)/kutils (KSettings::Dispatcher) void __thiscall KSettings::Dispatcher::DispatcherPrivate::unregisterComponent(class QObject *): componentName= "kdevplatformproject" refcount= 0 [4720] kdevelop(4720)/kdevplatform (language) __thiscall KDevelop::DUChainPrivate::~DUChainPrivate(void): Destroying [4720] QWaitCondition: Destroyed while threads are still waiting [4720] kdevelop(4720)/kio (Slave) void __thiscall KIO::Slave::kill(void): killing slave pid 2040 ( "trash://" ) [4720] kdevelop(4720)/kio (Slave) void __thiscall KIO::Slave::kill(void): killing slave pid 1552 ( "file://" ) [3872] Debug:klauncher(3872)/kio (KLauncher) void __thiscall KLauncher::slotFinished(int,enum QProcess::ExitStatus): process finished exitcode= 0 exitStatus= 0 [4720] kdevelop(4720)/kio (Slave) void __thiscall KIO::Slave::kill(void): killing slave pid 3852 ( "file://" ) [3872] Debug:klauncher(3872)/kio (KLauncher) void __thiscall KLauncher::slotFinished(int,enum QProcess::ExitStatus): process finished exitcode= 0 exitStatus= 0 [3872] Debug:klauncher(3872)/kio (KLauncher) void __thiscall KLauncher::slotFinished(int,enum QProcess::ExitStatus): process finished exitcode= 0 exitStatus= 0 [4720] zone still contained 2 blocks [4864] drkonqi(4864) class CrashedApplication *__thiscall KCrashBackend::constructCrashedApplication(void): Executable is: "L:/bin/kdevelop" [4864] drkonqi(4864) class CrashedApplication *__thiscall KCrashBackend::constructCrashedApplication(void): Executable exists: false [4864] drkonqi(4864) bool __cdecl DrKonqi::init(void): Enabling drkonqi crash catching Just an idea: In utils/katecmd.h, we have one single KCompletion object, shared with several line edits (all the command line-edit (F7)). KCompletion m_cmdCompletion; // shared completion object for all KateCmdLineEdits in each KTE::View Maybe this completion object is invalid, because it's deleted in windows and not in linux? Ok, I found out again yesterday evening that I already debugged this nearly a year ago; the problem is indeed the KCompletion objects. It seems as if deleted pointers are not set to 0x0 on msvc debug builds, but instead to some other values (0xfeeefeee). This also means that checks like if(0xfeeefeee) do not return the same results as on gcc... I will debug this in kdelibs, and see how I can fix that error. Thanks for the pointers to katecmd though ;-) *** This bug has been marked as a duplicate of bug 243375 *** |