Summary: | Crash when starting the project | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Stefan Stammberger <sstammberger> |
Component: | general | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | CC: | davide.rondini, dima, Maxim.Prohorenko |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Stefan Stammberger
2009-07-21 21:14:19 UTC
your installation is somehow broken. Might be it picks up two different execute plugin from two different kdevelop installations. Or your build is somehow broken. Either way, I suggest to remove any kdevelop/kdevplatform installation you have (including any packages) and also any builddirectories you have from either of the two. Then rebuild+reinstall both. *** Bug 209495 has been marked as a duplicate of this bug. *** *** Bug 209617 has been marked as a duplicate of this bug. *** *** Bug 235595 has been marked as a duplicate of this bug. *** Created attachment 43257 [details] New crash information added by DrKonqi I figured out the repro steps: - Build and install KDevelop - Set KDEDIRS and run kbuildsycoca4 - Start KDevelop - Unset KDEDIRS and run kbuildsycoca4 again, without closing KDevelop - Start debugging an application... KDevelop crashes. Note that these steps don't constradict the instructions at http://www.kdevelop.org/mediawiki/index.php/KDevelop_4/compiling. They don't say anything about not running kbuildsycoca4 after starting KDevelop. This also explains why (Sorry, accidentally submitted the report before I finished typing...) This also explains why KDevelop works for a while, then randomly crashes: some app causes kbuildsyscoca4 to run, without KDEDIRS being set. (In reply to comment #6) > (Sorry, accidentally submitted the report before I finished typing...) > > This also explains why KDevelop works for a while, then randomly crashes: some > app causes kbuildsyscoca4 to run, without KDEDIRS being set. Well, I'm sorry but thats a setup issue on your system. That is not supported and won't be. Basically you're breaking KDE-internal caches with this and its not just kdevelop that would break down here. Sure, but my point is, the build instructions don't make this clear. I'm used to setting variables like LD_LIBRARY_PATH when running a program I compiled from sources - and expected KDEDIRS to work the same way. Anyway, the wiki page should probably be updated to say that KDEDIRS needs to be set to the same value across the whole KDE session. *** Bug 237167 has been marked as a duplicate of this bug. *** |