| Summary: | KDevelop crashed when rebuilding an active CMake project [KDevelop::IPlugin::extensions (this=0x0)] | ||
|---|---|---|---|
| Product: | [Developer tools] kdevplatform | Reporter: | Jonathan Maasland <dreamCatalyst> |
| Component: | shell | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | aaronw, aleixpol, deszynski, kubek-93, magnus.reftel, Maxim.Prohorenko, percy.camilo.ta, petermichaelclausen |
| Priority: | NOR | ||
| Version: | 0.9.94 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 5.0.0 | |
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi STDERR from kdevelop, with added kdebugdiag output crash report from previous log-output 70951: STDERR from kdevelop, with added kdebugdiag output |
||
|
Description
Jonathan Maasland
2011-02-14 11:03:19 UTC
Are you sure everything is properly installed? Looks like you're missing the cmakebuilder plugin. no, this looks stranger than that: i->extension has a valid this ptr (result from a pluginForExtension query) when called from the cmakemanager, but once it calls extensions inside it seems to be zero - which makes no sense. ABI breakage? Jonathan, please make sure both KDevplatform and KDevelop are properly up2date and installed. I checked out and compiled both KDevelop and KDevplatform at the same time. (feb. 8th). Yes I've run kbuildsycoca4 after installing (with the proper KDEDIRS env var). I'm pretty confident it's not the install. Unfortunately I've not been able to reproduce this bug. Created attachment 60019 [details]
New crash information added by DrKonqi
kdevelop (4.2.60) on KDE Platform 4.6.3 (4.6.3) using Qt 4.7.2
- What I was doing when the application crashed:
1 Select simple target from list
2 Right click and build target
3 Crash
Reproduced not every time.
Build from git
kate adfe1a5
kdevplatform 272dfd2
kdevelop b3104e2
-- Backtrace (Reduced):
#6 QList (l=) at /usr/include/QtCore/qlist.h:118
#7 QStringList (l=) at /usr/include/QtCore/qstringlist.h:71
#8 KDevelop::IPlugin::extensions (this=0x0) at /home/maxim/src/kdevelop-all/kdevplatform/interfaces/iplugin.cpp:155
#9 0x00007fc2f94e4cd3 in extension<KDevelop::IProjectBuilder> (this=0x0) at /home/maxim/kde/usr/include/kdevplatform/interfaces/iplugin.h:183
#10 CMakeManager::builder (this=<optimized out>) at /home/maxim/src/kdevelop-all/kdevelop/projectmanagers/cmake/cmakemanager.cpp:871
You have some installation problem here. Make sure kbuildsycoca is run and to be matching kdevplatform and kdevelop versions. Created attachment 60461 [details]
New crash information added by DrKonqi
kdevelop (4.2.60) on KDE Platform 4.6.3 (4.6.3) using Qt 4.7.2
- What I was doing when the application crashed:
1 Select simple target from list
2 Right click and build target
3 Crash
It crashed some times. But work in other time. I'm sure it is not installation problem.
kdevplatform b971b7a7d566da53e5848cc68adfb20970944622
kdevelop 5c9db99e951cc6d1b565eab91b9557205e7f2ff0
I use this script to run
#!/bin/bash
export KATE_DIR=~/kde/usr
export PATH=$KATE_DIR/bin:$PATH
export LD_LIBRARY_PATH=$KATE_DIR/lib:$LD_LIBRARY_PATH
export KDEDIR=$KATE_DIR
export KDEDIRS=$KDEDIR
export XDG_DATA_DIRS=$XDG_DATA_DIRS:$KATE_DIR/share
# update KDE's system configuration cache
kbuildsycoca4
# start app
$@
-- Backtrace (Reduced):
#6 QList (l=) at /usr/include/QtCore/qlist.h:118
#7 QStringList (l=) at /usr/include/QtCore/qstringlist.h:71
#8 KDevelop::IPlugin::extensions (this=0x0) at /home/maxim/src/kdevelop-all/kdevplatform/interfaces/iplugin.cpp:155
#9 0x00007f00b0770cd3 in extension<KDevelop::IProjectBuilder> (this=0x0) at /home/maxim/kde/usr/include/kdevplatform/interfaces/iplugin.h:183
#10 CMakeManager::builder (this=<optimized out>) at /home/maxim/src/kdevelop-all/kdevelop/projectmanagers/cmake/cmakemanager.cpp:871
Created attachment 66491 [details]
New crash information added by DrKonqi
kdevelop (4.2.60) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.3
- What I was doing when the application crashed:
Rebuild a C++ project based on cmake builder.
- Unusual behavior I noticed:
The editor: when I select some text only select some part of the text ... this was 'fixed' enabling static wordwrap :S
- Custom settings of the application:
I set the compiler env var CPLUS_INCLUDE_PATH and the C_INCLUDE_PATH
-- Backtrace (Reduced):
#6 QList (l=<error reading variable: Cannot access memory at address 0x20>, this=0x7fff37294170) at /usr/include/qt4/QtCore/qlist.h:118
#7 QStringList (l=<error reading variable: Cannot access memory at address 0x20>, this=0x7fff37294170) at /usr/include/qt4/QtCore/qstringlist.h:71
#8 KDevelop::IPlugin::extensions (this=0x0) at /home/percy/apps/local/src/kdevplatform/interfaces/iplugin.cpp:155
#9 0x00007f3d05140da3 in extension<KDevelop::IProjectBuilder> (this=0x0) at /home/percy/apps/local/include/kdevplatform/interfaces/iplugin.h:183
#10 CMakeManager::builder (this=<optimized out>) at /home/percy/apps/local/src/kdevelop/projectmanagers/cmake/cmakemanager.cpp:966
reopening. my guess is that the builder gets unloaded (was not used anymore) and then fails to get reloaded or something like that. has anyone found a way to reproducibly trigger this crash? Well, if it's the bug milian said, reassigning to kdevplatform. *** Bug 298679 has been marked as a duplicate of this bug. *** I've activated kdebugdialog as Miriam suggested in Bug 298679 and since that I did not experience any crashes... I'll try to deactivate kdebugdialog again and see if I can reproduce the crash, but right now I'm just happy with a stable kdevelop :-) Created attachment 70951 [details]
STDERR from kdevelop, with added kdebugdiag output
.. and of course after I wrote the above, kdevelop started crashing again on build.
Created attachment 70952 [details]
crash report from previous log-output 70951: STDERR from kdevelop, with added kdebugdiag output
crash report from previous log-output: 70951: STDERR from kdevelop, with added kdebugdiag output
*** Bug 279864 has been marked as a duplicate of this bug. *** *** Bug 327546 has been marked as a duplicate of this bug. *** *** Bug 321266 has been marked as a duplicate of this bug. *** *** Bug 343112 has been marked as a duplicate of this bug. *** I think with the move to JSON-based plugin metadata these kind of crashes are gone. Marking as resolved |