THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 06/02/2003 at 06:55, xxxxxxxx wrote:
It is not impossible to find bugs without a debugger, it is just harder and more skill is involved, it wasn't that many years ago us programmers didn't have debuggers of the standards we have now. I do know some people that don't use a debugger at all, or rarely. One of the main ways to do debugging, even when you have a debugger! is to output text to the console or a file, logging what is going on compared to what you think should be happening.
If you have MS VisualStudio you have an excellent debugger that works fine! I get the impression you don't know how to setup the project for debugging. The best way is to place your plugins source folder in the Plugins folder for CINEMA, then in the Project settings, set the Link output file without a path so it creates the CDL in the path of your plugin. Also in the Project settings, in the Debug tab, set the executable for the session to CINEMA. That is it! Now just start the debug (press F5 or click Go), it will load CINEMA, and you plugin can be debugged during runtime.
I think you have misunderstood memory/object allocation. If you have inserted an object/tag into the document, CINEMA will take care of it. You ONLY need to free objects/tags if they are not linked to a document, for example, if you create a temporary object, then when you are finished with it, you use the ::Free() for that object/tag type. If allocating memory, when you are finished you always free it.
Also, ensure you have a c4d_debug.txt file in your plugins folder, CINEMA will open a debug console giving you object/memory allocation leaks at exit and other useful info.