What the hell! :)

Helper

On 28/08/2013 at 10:39, xxxxxxxx wrote:

User Information:
Cinema 4D Version:   R13
Platform:   Windows ;
Language(s) :     C++ ;

---------
My plugin was working and now it is completely broken.

This is the bug report text:

"CINEMA_4D_Crash_Report_WINDOWS
{
"

That is it. I have no clue as to the problem. I tried the previous VS2005 project and it has the same problem. The VS2010 project was working and now it is completely screwed - and I have no idea what is going wrong at all. All of my recent changes were beyond the basic plugin loading and stuff. What the hell is going on here? I've commented out swaths of code and still nothing. Not even PluginStart() is printing at the beginning - so I think there is something very deeply wrong in this situation. Comparing project settings between mine and cinema4dsdk shows no relevant differences. This is infuriating. I've never had a plugin just not load with no idea of the cause whatsoever. Grrrrrrrr.

Helper

On 28/08/2013 at 12:01, xxxxxxxx wrote:

Originally posted by xxxxxxxx

<ADDRESS>
User Information:
Cinema 4D Version:   R13
Platform:   Windows ;
Language(s) :
C++ ;

---------
</ADDRESS> My plugin was working and now it is completely broken.This is the bug report text:"CINEMA_4D_Crash_Report_WINDOWS{"That is it. I have no clue as to the problem. I tried the previous VS2005 project and it has the same problem. The VS2010 project was working and now it is completely screwed - and I have no idea what is going wrong at all. All of my recent changes were beyond the basic plugin loading and stuff. What the hell is going on here? I've commented out swaths of code and still nothing. Not even PluginStart() is printing at the beginning - so I think there is something very deeply wrong in this situation. Comparing project settings between mine and cinema4dsdk shows no relevant differences. This is infuriating. I've never had a plugin just not load with no idea of the cause whatsoever. Grrrrrrrr.

Most likely a serious memory trasher that prevents the stack walker from resolving the call stack and/or writing down the crash info.

Best regards,

Wilfried

Helper

On 28/08/2013 at 23:58, xxxxxxxx wrote:

Finally found it. One little, simple thing that didn't appear to pose a problem before posed it last night.