search

coolfluid / coolfluid3

COOLFluiD is a collaborative simulation environment focused on complex multi-physics simulations
http://coolfluid.github.com
76 stars 77 forks source link

clang linking crashes for utest-proto-heat and other UFEM tests #207

Closed wdeconinck closed 12 years ago

wdeconinck commented 12 years ago

Since the last merge from barche, clang crashes again at linking utest-proto-heat, and other utest-proto executables. Only the UFEM/tests have this problem. The proto tests for cf3/solver don't have any problems.

The crash occurs both with clang 3.0 and clang 3.1. I realize this is probably a bug in clang, which should give a proper linking error message, but since this crash only started occurring since latest merge, maybe it is possible an error is introduced in cf3 nevertheless.

Since clang is one of our main supported compilers, this issue is marked as fatal and urgent. barche is assigned being the expert proto-clang-crasher :)

[ 85%] Building CXX object plugins/UFEM/test/CMakeFiles/utest-proto-heat.dir/utest-proto-heat.cpp.o
Linking CXX executable utest-proto-heat
clang: error: unable to execute command: Segmentation fault: 11
clang: error: linker command failed due to signal 2 (use -v to see invocation)
clang: note: diagnostic msg: Please submit a bug report to http://developer.apple.com/bugreporter/ and include command line arguments and all diagnostic information.
clang: warning: treating 'c' input as 'c++' when in C++ mode, this behavior is deprecated
clang: warning: treating 'c' input as 'c++' when in C++ mode, this behavior is deprecated
clang: warning: treating 'c' input as 'c++' when in C++ mode, this behavior is deprecated
clang: warning: treating 'c' input as 'c++' when in C++ mode, this behavior is deprecated
clang: note: diagnostic msg: Error generating preprocessed source(s).
make[2]: *** [plugins/UFEM/test/utest-proto-heat] Error 254
make[1]: *** [plugins/UFEM/test/CMakeFiles/utest-proto-heat.dir/all] Error 2
make: *** [all] Error 2
tlmquintino commented 12 years ago

Yep, I confirm the same behaviour - is this a clang-macosx thing? Does clang 3.0 on Linux reproduces the same result?

The linker behaves slightly differently from macosx to Linux.

barche commented 12 years ago

I'm upgrading my home machine to get clang 3.0. On Clang 2.9, I have no problems in linux.

wdeconinck commented 12 years ago

My VUB iMac is up and running again with new hard disk after the crash. Soon this error will appear on dashboards near you. 2 builds are coming: a minimal one having only boost and openmpi, and a recommended build having the recommended deps.

barche commented 12 years ago

This does not happen with clang 3.0 on linux, so it must be mac-specific. Given that it is a segfault, I'd say hunt it down: get a linker with debug symbols, get a backtrace, and send it to the clang developers. Maybe before that, adding the "-v" option to clang will already give more clues.

wdeconinck commented 12 years ago

Miraculously this problem fixed itself, as it also came by itself :) Hurray!

Still using the same configuration as before. Also the OSX dashboard builds show this.