Summary: | kdevelop cmake project manager crashes when using illegal `include_directories` | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | alonso schaich <alonsoschaich> |
Component: | general | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | aleixpol |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
crash dump
command line output |
Description
alonso schaich
2009-09-14 14:57:45 UTC
Created attachment 36942 [details]
crash dump
seems the one i copy-pasted into the bug report text field isn't propperly showing
(In reply to comment #0) > when opening a cmake project that contains illegal `include_directories` > directives, kdevelop crashes. > fixing the include_directories enables kdevelop to load the project but i think > kdevelop shouldn't crash because of something like that. What does "illegal" mean? Can you post your cmakelists.txt? An example would be great, yes, since the code that's crashing it's not inside cmake code. if you could provide a backtrace with debug info that would be great as well. (In reply to comment #2) > (In reply to comment #0) > > when opening a cmake project that contains illegal `include_directories` > > directives, kdevelop crashes. > > fixing the include_directories enables kdevelop to load the project but i think > > kdevelop shouldn't crash because of something like that. > > What does "illegal" mean? Can you post your cmakelists.txt? with illegal i meant URLs that do not exist. CMakeLists.txt: project(ren) include_directories(${wileynet_SOURCE_DIR}/libWileynet ${wileynet_SOURCE_DIR}/Server/libStorageBackend ${ren_SOURCE_DIR}) set(ren_SRC ConfigurationManager.cc NetworkInterface.cc Wiley.cc infrastructure.cc main.cc ) set(ren_MOC_HDR ConfigurationManager.h NetworkInterface.h Wiley.h ) qt4_automoc(${ren_SRC}) QT4_WRAP_CPP(ren_MOC_SRC ${ren_MOC_HDR}) add_executable(ren ${ren_SRC} ${ren_MOC_SRC}) target_link_libraries(ren StorageBackend RenProcessors ${COMMON_LIBS} ${QT_QTSQL_LIBRARY}) install( TARGETS ren DESTINATION bin ) install( FILES share/template DESTINATION share/wileynet ) add_subdirectory(processors) actually none of those include directories ( other then ren_SOURCE_DIR ) exists. (In reply to comment #3) > An example would be great, yes, since the code that's crashing it's not inside > cmake code. > > if you could provide a backtrace with debug info that would be great as well. i hope having debug symbols in only kdevplatform, kdevelop and kdelibs is enough: #0 0x00007ffff30ac095 in raise () from /lib64/libc.so.6 #1 0x00007ffff30ad4c0 in abort () from /lib64/libc.so.6 #2 0x00007ffff30e689d in __libc_message () from /lib64/libc.so.6 #3 0x00007ffff30ebe46 in malloc_printerr () from /lib64/libc.so.6 #4 0x00007ffff30f148b in _int_realloc () from /lib64/libc.so.6 #5 0x00007ffff30f18c0 in realloc () from /lib64/libc.so.6 #6 0x00007ffff4c70f8e in QListData::realloc(int) () from /usr/lib64/qt4/libQtCore.so.4 #7 0x00007ffff4c71192 in QListData::append() () from /usr/lib64/qt4/libQtCore.so.4 #8 0x00007fffd485bea1 in QList<QString>::append (this=0x7fffd4ae91a8, t=...) at /usr/include/qt4/QtCore/qlist.h:429 #9 0x00007fffd4871ef9 in QStringList::operator<< (this=0x33d7, str=...) at /usr/include/qt4/QtCore/qstringlist.h:87 #10 0x00007fffd4879ca8 in CppTools::setupStandardIncludePaths (includePaths=<value optimized out>) at /mnt/tmpfs/portage/dev-util/kdevelop-9999/work/kdevelop-9999/languages/cpp/setuphelpers.cpp:89 #11 0x00007fffd48705b9 in CppUtils::standardIncludePaths () at /mnt/tmpfs/portage/dev-util/kdevelop-9999/work/kdevelop-9999/languages/cpp/cpputils.cpp:186 #12 0x00007fffd485cbc2 in IncludePathComputer::computeBackground (this=0x7fffc40285f0) at /mnt/tmpfs/portage/dev-util/kdevelop-9999/work/kdevelop-9999/languages/cpp/includepathcomputer.cpp:118 #13 0x00007fffd4861e6e in CPPParseJob::includePaths (this=0x3955e50) at /mnt/tmpfs/portage/dev-util/kdevelop-9999/work/kdevelop-9999/languages/cpp/cppparsejob.cpp:244 #14 0x00007fffd4861f09 in CPPParseJob::includePathUrls (this=0x33d7) at /mnt/tmpfs/portage/dev-util/kdevelop-9999/work/kdevelop-9999/languages/cpp/cppparsejob.cpp:228 #15 0x00007fffd486ce30 in PreprocessJob::run (this=0x39bf2e0) at /mnt/tmpfs/portage/dev-util/kdevelop-9999/work/kdevelop-9999/languages/cpp/preprocessjob.cpp:190 #16 0x00007ffff6479d71 in ThreadWeaver::JobRunHelper::runTheJob (this=0x7fffca82ceb0, th=0x7fffd811a540, job=0x39bf2e0) at /mnt/tmpfs/portage/kde-base/kdelibs-4.3.1-r1/work/kdelibs-4.3.1/threadweaver/Weaver/Job.cpp:106 #17 0x00007ffff6479f49 in ThreadWeaver::Job::execute (this=0x39bf2e0, th=0x7fffd811a540) at /mnt/tmpfs/portage/kde-base/kdelibs-4.3.1-r1/work/kdelibs-4.3.1/threadweaver/Weaver/Job.cpp:135 #18 0x00007ffff647be83 in ThreadWeaver::JobCollectionJobRunner::execute (this=0x22f1400, t=0x7fffd811a540) at /mnt/tmpfs/portage/kde-base/kdelibs-4.3.1-r1/work/kdelibs-4.3.1/threadweaver/Weaver/JobCollection.cpp:82 #19 0x00007ffff647bde0 in ThreadWeaver::JobCollection::execute (this=0x3955e50, t=0x7fffd811a540) at /mnt/tmpfs/portage/kde-base/kdelibs-4.3.1-r1/work/kdelibs-4.3.1/threadweaver/Weaver/JobCollection.cpp:228 #20 0x00007ffff647940f in ThreadWeaver::ThreadRunHelper::run (this=0x7fffca82cfd0, parent=0x17010b0, th=0x7fffd811a540) at /mnt/tmpfs/portage/kde-base/kdelibs-4.3.1-r1/work/kdelibs-4.3.1/threadweaver/Weaver/Thread.cpp:95 #21 0x00007ffff6479554 in ThreadWeaver::Thread::run (this=0x7fffd811a540) at /mnt/tmpfs/portage/kde-base/kdelibs-4.3.1-r1/work/kdelibs-4.3.1/threadweaver/Weaver/Thread.cpp:142 #22 0x00007ffff4c3f3c2 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #23 0x00007ffff49c9624 in start_thread () from /lib64/libpthread.so.0 #24 0x00007ffff314756d in clone () from /lib64/libc.so.6 #25 0x0000000000000000 in ?? () i'll put kdevelop's console output into an attachment... Created attachment 36945 [details]
command line output
Thanks, so this is yet another incarnation of MALLOC_CHECK_ set to abort the app. See the duplicate report(s) for a workaround. *** This bug has been marked as a duplicate of bug 206775 *** |