Summary: | crash when building | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Diggory Hardy <kde2> |
Component: | general | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | deszynski, neil, olivier.jg |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | 4.2.0 | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Diggory Hardy
2011-04-27 15:13:45 UTC
Sorry, updates to KDE packages were in progress when this crash happened -- a very likely cause. Created attachment 59546 [details]
New crash information added by DrKonqi
kdevelop (4.2.2) on KDE Platform 4.6.2 (4.6.2) using Qt 4.7.2
- What I was doing when the application crashed:
Building after importing a Makefile based project
- Custom settings of the application:
I am using a project imported from a makefile rather than a native kdevelop project type. This is using the KDevelop packaged with Ubuntu 11.04 rather than custom sources of the previous reporter of this defect. Hence I believe this is a genuine defect.
-- Backtrace (Reduced):
#7 0x00007fbaaf409394 in KDevelop::BuilderJobPrivate::addJob (this=0x4c28ed0, t=<value optimized out>, item=0x4bbb280) at ../../project/builderjob.cpp:70
#8 0x00007fba8337e8c1 in BuildItemBuilderJob::BuildItemBuilderJob (this=0x49d2580, t=KDevelop::BuilderJob::Build, items=...) at ../../../plugins/projectmanagerview/builditembuilderjob.cpp:35
#9 0x00007fba83372752 in ProjectManagerViewPlugin::runBuilderJob (this=<value optimized out>, t=KDevelop::BuilderJob::Build) at ../../../plugins/projectmanagerview/projectmanagerviewplugin.cpp:348
#10 0x00007fba83375bdc in ProjectManagerViewPlugin::qt_metacall (this=0x3373490, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7ffff4089080) at ./projectmanagerviewplugin.moc:109
[...]
#12 0x00007fbab1c8d112 in QAction::triggered (this=<value optimized out>, _t1=false) at .moc/release-shared/moc_qaction.cpp:263
Reopening then. In the meantime I've also experienced this crash several more times. I think each time kdevelop had already been running a while and had some unsaved documents (though it could just be that those were the times I remember more clearly ;-) ). I've been using custom CMake files. first: @Neil: unrelated crash secondly: @Diggory: Make sure to remove system wide installed kdev installations if you compile kdev on your own. your bt contains ... from /usr/local/lib/kde4/kdevcmakemanager.so which can lead to all sorts of issues when combined with stuff in /home/dhardy/code/download/kdevelop/kdevplatform-1.2.2/... I installed the kdevelop download I compiled in /usr/local. Distributions never put stuff there. If I don't set KDEDIRS=/usr/local:$KDEDIRS then the cmakemanager plugin (as I think all plugins) aren't found either. I didn't actually realise it was using the build path... though it shouldn't make a difference. I've not had this bug occur quite so recently... either it's sporadic or some other system updates have solved it somehow. indeed, my bad. So you installed kdevelop without debug symbols? No clue what is going on here :-/ Sorry. I'll re-build with debug symbols then, but as I said I haven't experienced this crash in the last couple of weeks or so. CMAKE_BUILD_TYPE: I often use RelWithDebInfo. This is probably OK for a stack trace? At any rate I didn't think debugfull was supported as the wiki suggested. If this is valid, it looks a bit like something that was fixed a little while ago. Anyone feel free to reopen if you hit this again with a good bt. Looks like someone already has put up a good bt for this, probably another invalid project item issue. *** Bug 279864 has been marked as a duplicate of this bug. *** FYI: Piotr mentioned that his crash is probably due to missing dependencies and happens every time. The crash I posted about here happened sporadically during normal usage, and when restarting kdevelop it would build fine (without any changes to source/config files). I think these are separate issues. That said I think Olivier was right to close this report; I haven't experienced this crash in months so presumably it was fixed in some update. I won't close now though because Piotr's report may well still be valid. closing this one and reviving 279864 |