btSequentialImpulseConstraintSolver function error ?

[going]

hey, I'm now making unmanaged to managed wrapper class to use bullet on windows forms

but when I execute the wrapper class it always got an error in this section

Code: Select all

// #pragma unmanaged zone

btSequentialImpulseConstraintSolver* solver = new btSequentialImpulseConstraintSolver;

and the error is

Code: Select all

Debug Assertion Failed;

Program...
File: f\dd\vctools\crt_bld\self_x86\crt\src\dbgheap.c
Line: 1511

Expression: _CtrIsValidHeapPointer(pUserData)

For information on how your program can cause an assertion
failure, see the visual C++ docuentation on asserts.

(press retry to debug the application)

and i tried multithread ver also, but i got the same errrors.
I'm compiling this code in visual studio 2008.

is there any way to solve this error?

[Erwin Coumans]

pUserData?

Do you have a full callstack at the moment of the assert?
Thanks,
Erwin

[going]

thanks! hi this is the full callstack

Code: Select all

     msvcr90d.dll!_msize_dbg(void * pUserData=0x95559c03, int nBlockUse=2)  ?(line) 1511 + 0x30 ???(byte)    C++
     msvcr90d.dll!_dllonexit_nolock(int (void)* func=0x9511feb3, void (void)* * * pbegin=0x0012eee8, void (void)* * * pend=0x0012eee0)  ? 295 + 0xd ???    C
     msvcr90d.dll!__dllonexit(int (void)* func=0x9511feb3, void (void)* * * pbegin=0x0012eee8, void (void)* * * pend=0x0012eee0)  ? 273 + 0x11 ???    C
     irrlicht_form.exe!_onexit(int (void)* func=0x004462b0)  ? 110 + 0x1b ???    C
     irrlicht_form.exe!atexit(void (void)* func=0x004462b0)  ? 127 + 0x9 ???    C
     irrlicht_form.exe!`dynamic initializer for 'g_gimpact_cf''()  ? 878 + 0xa ???    C++
     [?????]   
     [??????????????????????????mscorwks.dll ?????????????????????]   
     kernel32.dll!7c83971e()    
     kernel32.dll!7c809a69()    
     kernel32.dll!7c83971e()    
     kernel32.dll!7c809a69()    
>    mscoree.dll!7900b1b3()    
     kernel32.dll!7c816fd7()    

not related to bullet?

[sparkprime]

To be fair, I don't see any mention of Bullet in the call stack... But the problem could still have originated from somewhere else. You should do some digging.