kdev-clang and clang/llvm 3.5?

[Kevin Funk]

On Friday 30 January 2015 11:41:37 René J.V. Bertin wrote:
> Hi,
> 
> The output from kdev-clang's cmake file claims clang >= 3.4 is required, but
>  the file has a hard-coded version 3.4 requirement.

Nope, that's a *minimum* requirement.

The problem is that our find script doesn't really reflect it. It will just 
look for llvm-config-VERSION and doesn't look for other versions of that 
executable (i.e. llvm-config-3.5, llvm-config-3.6, ...). Anyhow, you should be 
able to work-around that by setting LLVM_ROOT, as said in an earlier post.

I have improving the find script on my TODO. Since 3.5, LLVM even ships CMake 
config files, but for instance on Ubuntu, those are broken. Thus, we cannot 
simply use them.

>  Clang 3.4 is about as
> outdated as gcc 4.8 is (probably more, clang being younger than gcc as the
> version numbers indicate), and I thus have clang 3.5 installed (clang 3.5.1
> with packaging borrowed from Debian:
> https://launchpad.net/~rjvbertin/+archive/ubuntu/llvm/+packages).
> 
> kdev-clang builds and works when I replace that with 3.5, but I just got
> this crash doing a duchainify in the kdevplatform source tree:
> 
> Thread 2 (Thread 0x7f576a7fb700 (LWP 1306)):
> [KCrash Handler]
> #6  clang::cxtu::isASTReadError (AU=0x0) at
> /build/buildd/llvm-toolchain-3.5-3.5-8~debiansid-rjvb/tools/clang/tools/lib
> clang/../../include/clang/Frontend/ASTUnit.h:633 #7  0x00007f5777575c15 in
> clang_parseTranslationUnit_Impl (UserData=<optimized out>) at
> /build/buildd/llvm-toolchain-3.5-3.5-8~debiansid-rjvb/tools/clang/tools/lib
> clang/CIndex.cpp:2912 #8  0x00007f5776826a73 in operator() (this=<synthetic
> pointer>) at
> /build/buildd/llvm-toolchain-3.5-3.5-8~debiansid-rjvb/include/llvm/ADT/STLE
> xtras.h:106 #9 
> llvm::CrashRecoveryContext::RunSafely(llvm::function_ref<void ()>)
> (this=<optimized out>, Fn=...) at
> /build/buildd/llvm-toolchain-3.5-3.5-8~debiansid-rjvb/lib/Support/CrashReco
> veryContext.cpp:318 #10 0x00007f5776826ad7 in RunSafelyOnThread_Dispatch
> (UserData=0x7f576b7fc490) at
> /build/buildd/llvm-toolchain-3.5-3.5-8~debiansid-rjvb/lib/Support/CrashReco
> veryContext.cpp:366 #11 0x00007f5776854a1d in ExecuteOnThread_Dispatch
> (Arg=<optimized out>) at
> /build/buildd/llvm-toolchain-3.5-3.5-8~debiansid-rjvb/lib/Support/Threading
> .cpp:40 #12 0x00007f57aff49182 in start_thread (arg=0x7f576a7fb700) at
> pthread_create.c:312 #13 0x00007f57b025a00d in clone () at
> ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Known [1]. But this doesn't crash KDevelop, right? It just results in an 
internal libclang "crash".

[1] http://llvm.org/bugs/show_bug.cgi?id=22282 (reported by me)
> 
> Thoughts?
> 
> R.
> _______________________________________________
> KDevelop mailing list
> KDevelop at kde.org
> https://mail.kde.org/mailman/listinfo/kdevelop

-- 
Kevin Funk | kfunk at kde.org | http://kfunk.org