views:

912

answers:

3

I upgrade to snow leopard and xcode 3.2 this week, and since that I'm having problems with CDT. I tryed this in CDT 5 (ganymede) and CDT 6 (galileo).

If I try to debug the application using launcher "Standard Create Process Launcher", it delays about 10 seconds to actually get in the debugging breakpoint, which is very odd.

If I use as launcher "GDB (DSF) Create Process Launcher" it work at the speed I expect, but the variables tab that show me what's going on in the current scope show the variable values like that:

"Failed to execute MI command: -var-update 1 var2 Error message from debugger back end: Variable object not found Failed to execute MI command: -var-update 1 var1 Error message from debugger back end: Variable object not found"

I don't have any idea how to solve one or the other issue, any of them will let me work up to speed.

thanks in advance.

A: 

I am having the same exact problem. I found this website which suggests the fix for compiling as i386. But that results in stack overflow error in my code, which does not have any problems normally or before Snow Leopard.

http://blog.christianleberfinger.de/?p=167

Can

Can Ozcan
A: 

I too am having this exact problem. I am highly considering switching back to Leopard...

A: 

Same here and I'm using Leopard.

The "GDB (DSF) Create Process Launcher" is said to be unstable, see here http://stackoverflow.com/questions/1270285/trouble-debugging-c-using-eclipse-galileo-on-mac

And I'm experiencing worse with "Standard Create Process Launcher", takes minutes to launch, while eclipse is only using 5% of the cpu.

Eyoka