-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault for all the tests in the development branch #210
Comments
Can you run just a single test (e.g., test #2) and copy its output? You can also try running the test with the debugger and posting the backtrace here. |
Apparently it's a problem with boost...
I will try deleting the build folder, maybe there's something old or from a different branch even after the "Clean All"... |
Still the same problem. The applications are running though. It's |
Hmm, really curious. Which boost version are you using? Also what does
report? |
I have this in my main CMake file:
but I see no boost directory in my build folder. Is that normal? Where should I run the |
Maybe
|
And the output from run CMake in case that may help...
|
Just for clarity: this only happens when you update to the FullDevelopmentBranch branch? If you delete the build folder, the CMakeLists.txt.user file and the boost folder (it should redownload and recompile it) does it run? To save compilation time, you can use the test_NumericalDerivative test, it has few if any dependencies. |
After that all the tests (except |
Good! Could you attach the error log? |
|
These failures seem to be small rounding errors only. Could you check if the branch you are on is fully up to date with the Tudat repository, and if so, open a new issue for these failures? |
I'm reopening the issue as it wasn't solved completely. On a fresh build of boost the problem is not there and all tests run. However, if cmake is ran followed by make, all unit tests result in segmentation faults. Closer inspection using otool revealed that the dynamic version of libboost_unit_test_framework-mt.dylib is added to the binaries dynamic library list. Even though it was compiled with the static version before. The CMakeCache.txt on first and second run remain unaltered, so it is likely an uncached variable inside add_boost.cmake that is causing a change in this behaviour. I will be working on a fix for this and update here. The solution for the time being is to remove all ".dylibs" from the stage/lib folder, which should not trigger CMake into rebuilding boost, but prefer the static versions of the libraries instead. |
The fix has been merged, so this issue can be closed. |
All the tests (except sofa-test) are throwing a SegFault exception in the FullDevelopmentBranch. I've tried cleaning all and building again, but still the same. Do you know what could be the problem?
The text was updated successfully, but these errors were encountered: