Community
Participate
Working Groups
Create a project with the following code: #include <stdlib.h> #include <stdio.h> int foo() { int x = 0; return x; // set a breakpoint here } int main(int argc, char *argv[]) { foo(); printf("Welcome to the Momentics IDE\n"); return EXIT_SUCCESS; } Set a breakpoint inside the function "foo", uncheck the "stop at main" option of the "Debugger" tab and launch a debug session. When program stops at the breakpoint select the second stack frame in the Debug view. The variables in the Variables view are shown as "<not responding>".
Jared, can you try this out and see what is going on?
Changing the priority since this is blocking our GA.
*** Bug 68677 has been marked as a duplicate of this bug. ***
(NOTE duplicate annotation was a user error)
Can you explain the difference you see between RC3 and 3.0 (we made no changes in the debug platform between RC3 and 3.0 that should effect this).
Darin, this is my fault. The problem is a result of the wrong design in the CDT debugger. The have a temporary fix and I hope we will address it for the next release.
The temporary solution has been submitted to the 2.0 branch. Changing the target milestone to "FUTURE".
Removing the P1 designation -- the target milestone is set to future....
Fixed in RC1.