ok , i was working on my Particle system for the last month , AND , i''ve just noticed that its crashs after couple of second after running it on the VC++ Debug mode. On the Release mode its run perfectly.... does anyone have any idea what could make the debug mode to crash?! or does something similar happend to someone in the past? Thanks alot , Roy. ************************* "Everything you know is wrong" - Bono *************************

- Goblineye Entertainment

Your using memory with uninitialized data which will have different values with different configurations. Run it in debug mode by selecting F5 (build->start debug->go) first to isolate the problem.

huh?
i almost sure that im initialized everything

hmmm... but when im runnning it on the debug mode (F5) its just stuck , i cant see where the problem is...

*************************
"Everything you know is wrong" - Bono
*************************

- Goblineye Entertainment

If you app is using DirectX fullscreen, Debug will most likely do you no good. Otherwise, it should take you back to the ide window, and there should be an arrow pointing to where it crashed. You can get the values of any variable in that code that has been encountered already by rightclick->quickwatch or mouse hover to get the basic stack value. At the bottom (or somewhere) there is a combobox called context which shows all the functions still running, and a listbox that lists some of the variables and their values. You can also insert breakpoints for it to stop anywhere in the code, and perform any of the many debug functions to control the execution of your code.

ok , i found where the bug is... in this line:
free(tmp_top);

but , HUH?!
its not making any sence coz i allocated memory for this pointer with calloc() , so , how come it cant be released?!

*************************
"Everything you know is wrong" - Bono
*************************

- Goblineye Entertainment

I have no idea why. Impossible to tell without seeing code. You''ll just have to go back through all the opened functions (use the context combo box) and check the values of all the pointers and variables to figure out where the values start to go bad (0xcccccccc is the value of an uninitialized pointer in debug mode). First though, I suggest recompiling it with that free line commented out to verify that is the problem.

Make sure you''re not freeing the same memory twice.

This is almost certainly some sort of memory corruption problem. When you use debug mode you get a slower allocator that does more checks for you. It''s probably crashing because the debug allocator found some problem that the release allocator just ignores.

-Mike