Weird Compiler error?

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 13/03/2007 at 04:06, xxxxxxxx wrote:

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

---------
Hi there,
i got a problem that is very weird. it only exists on a dualcore UB-Mac as i found out.
no matter where in the sourcecode the GetInfo() function of a BaseObject is inserted, the MAC freezes when the color picker from the Material Dialog is opened.

this is really very weird. the code doesn't have to be executed, it is enough if it's got compiled with other code. and the color picker freezes.

minimal example:

  
#include "c4d.h"  
  
void test()  
{  
BaseObject* test=NULL;  
if(test)  
test->GetInfo();  
}  
  
Bool PluginStart()  
{  
return True;  
}  
  
void PluginEnd()  
{  
}  
  
Bool PluginMessage(LONG id, void* data)  
{  
return TRUE;  
}  
  

as you see test is never executed, but the color picker freezes.
now can anybody tell me what that is? must be a XCode compiler error or anything.
would be nice if someone could test it on his machine. happens for me on a Dualcore Mac-Mini

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 15/03/2007 at 03:52, xxxxxxxx wrote:

sorry but I can not confirm this. i get no crashes here.

cheers,
Matthias

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 15/03/2007 at 08:50, xxxxxxxx wrote:

did you try it on a dual-core intel mac?
i only get this problem there, no problems with windows and single core macs.

thanks for testing so far

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 26/03/2007 at 00:52, xxxxxxxx wrote:

yes I tested it on a dual-core intel mac.

cheers,
Matthias

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 26/03/2007 at 04:51, xxxxxxxx wrote:

Make sure you remove any other plugins in your plugins folder before testing. Maybe another plugin is causing your plugin to crash.

Does it still crash when it´s the only plugin registered?

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 27/03/2007 at 00:09, xxxxxxxx wrote:

hey,
thanks for your replies,
yes i did remove all plugins, doesn't change anything.
it freezes each time i open the color picker from the Material.
the Debugger says something about GeDelete goes wrong.
i uploaded a file, perhaps you could try this. there's a compiled dylib inside and the project and source file. when you compile it yourself be sure to move the dylib out of the debug folder afterwards.

http://www.blackstar-solutions.de/files/freezeerror/brokenproj.zip

here's a screenshot:

thanks again.

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 27/03/2007 at 00:13, xxxxxxxx wrote:

hmm,
when i don't start it from the debugger it freezes when i close the material editor after changing the color.
someone is definitly corrupting my memory ;)