Summary: | Crash while parsing CMake project | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Blinov Vyacheslav <blinov.vyacheslav> |
Component: | general | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | beasley |
Priority: | NOR | ||
Version: | 4.4.1 | ||
Target Milestone: | 4.3.0 | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/kdevelop/5617be77912332b5f321fc41c4842e7d988ee19e | Version Fixed In: | |
Attachments: | minimal example CMakeLists txt that crashes KDevelop |
Description
Blinov Vyacheslav
2013-05-07 12:51:40 UTC
On changing this line back KDevelop opens this project fine! set(BOOST_ROOT $ENV{BOOST_LIBRARY}) cmake version 2.8.10.1 Boost version: 1.49.0 JFYI I'm using stock packages from Ubuntu 13.04 Sorry, My exact edit of CMakeLists.txt was to comment this line. After this CMakeLists.txt crashed. Uncommenting it back makes KDevelop work again. I am able to reproduce this again and again. Will try to create simple example project out of it. Created attachment 79753 [details]
minimal example CMakeLists txt that crashes KDevelop
Attached example that crashes KDevelop every time just on opening. If I'll create build directory and run cmake .. -DSP_COMMON_TARGET=linux before opening KDevelop, it won't crash now. rm build -rf and press Configure in KDevelop and it will crash again. Git commit 753a23d6065fe24b296c9c7fdabe31fb8f0b33db by Aleix Pol. Committed on 09/05/2013 at 02:30. Pushed by apol into branch '4.5'. Don't crash if we run list(FIND) without a find element M +6 -2 projectmanagers/cmake/parser/cmakeprojectvisitor.cpp http://commits.kde.org/kdevelop/753a23d6065fe24b296c9c7fdabe31fb8f0b33db Git commit 5617be77912332b5f321fc41c4842e7d988ee19e by Aleix Pol. Committed on 09/05/2013 at 02:30. Pushed by apol into branch 'master'. Don't crash if we run list(FIND) without a find element M +6 -2 projectmanagers/cmake/parser/cmakeprojectvisitor.cpp http://commits.kde.org/kdevelop/5617be77912332b5f321fc41c4842e7d988ee19e *** Bug 320181 has been marked as a duplicate of this bug. *** |