dAssert (0); - dNewton

[Slick]

I get a crash in newton.cpp at line 105.

The line in questions is:

Code: Select all

dAssert (0);

I just built using Cmake and the only change I made was to chamge the cmakelists.txt as follows:

Line 109 was:
if(NEWTON_STATIC_RUNTIME_LIBRARIES)
message ("link to static runtime libraries")
set(CMAKE_C_FLAGS_DEBUG "/MTd")
set(CMAKE_C_FLAGS_RELWITHDEBINFO "/MT")
set(CMAKE_C_FLAGS_RELEASE "/MT")
set(CMAKE_CXX_FLAGS_DEBUG "/MTd")
set(CMAKE_CXX_FLAGS_RELWITHDEBINFO "/MT")
set(CMAKE_CXX_FLAGS_RELEASE "/MT")

Now changed to:
if(NEWTON_STATIC_RUNTIME_LIBRARIES)
message ("link to static runtime libraries")
set(CMAKE_C_FLAGS_DEBUG "/MDd")
set(CMAKE_C_FLAGS_RELWITHDEBINFO "/MD")
set(CMAKE_C_FLAGS_RELEASE "/MD")
set(CMAKE_CXX_FLAGS_DEBUG "/MDd")
set(CMAKE_CXX_FLAGS_RELWITHDEBINFO "/MD")
set(CMAKE_CXX_FLAGS_RELEASE "/MD")

That may be unrelated but since it is a new project I don't know.

I am linking statically which is why I changed the Cmake as above.

Any ideas?

[Slick]

OK maybe I worked it out. It looks to me like an assertion is intentionally being thrown maybe for testing? However, this is the live version in github.

[JernejL]

there are often asserts in live versions, build a release versions or just comment them out.

[Slick]

I commented it out and as expected it works. The part that I don't understand is that this will always fall if assertions are on.

[Sweenie]

Julio usually adds a dAssert(0) when implementing something new or if a function isn't fully implemented etc.
It's seems he intended to add some transform functionallity to the dNewton class but never got around to it and just forgot to remove the assert.