[Bf-committers] Crash on Windows debug build with COLLADA

Benoit Bolsee benoit.bolsee at online.be
Mon Nov 16 11:23:43 CET 2009


Debug builds in Windows with COLLADA enabled will crash on startup with
this call stack:

r> >(const char * _Ptr=0x0012fe8c, const std::_Container_base_secure *
_Pstring=0x0012fe88)  Line 73 + 0x4d bytes C++
<char> >::erase()  + 0xce bytes C++
<char> >::clear()  + 0x8f bytes C++
  blender.exe!COLLADABU::URI::URI()  + 0xa8 bytes C++
  blender.exe!_GetFullPathNameW at 16()  + 0x324e06 bytes C++
  blender.exe!_initterm(void (void)* * pfbegin=0x022d73ac, void (void)*
* pfend=0x022dbc30)  Line 903 C
  blender.exe!_cinit(int initFloatingPrecision=1)  Line 307 + 0xf bytes
  blender.exe!__tmainCRTStartup()  Line 249 + 0x7 bytes C
  blender.exe!mainCRTStartup()  Line 182 C

It crashes on a assert that is part of the runtime validation of debug
build. The problem occurs because the COLLADA library makes use of STL
container and the binary representation won't match between a debug and
non debug version.

To fix this it would be necessary to build the collada library in debug
mode as well. Is it possible to do that?

For now I have disabled collada on debug build in the MSVC project


More information about the Bf-committers mailing list