flakey debugger problems

[Altera_Forum]

I'm finding the IDE debugger to be, well, quite flakey. Wondering if anyone has an idea what is behind these things before I give my friendly neigborhood FAE a call. These are some of the problems I've seen: 

 - when "stop at main() on startup" is checked it some time decides not to stop any way.  - If it does stop some times but it does not bring up the source file with the break point. It has the correct file name in the debug window "Thread[0]" list but it just can't seem to bring up the file. I can select the breakpoint in the breakpoint window and go to the file and line. Note that search paths are setup and correct (this worked better a couple of days ago).  -When stopped at a breakpoint without bringup the source I can step blindly but it does follow the expected execution path as indicated by the 'Thread[0]" stack trace.   - I often get a pop up window saying there was an error and to "see error log" on hitting a break point. The only log I've found is a .log file in the eclipse directory. It has lines like this:  MESSAGE Scanner Exception: null ENTRY org.eclipse.cdt.core 4 4 Nov 05, 2004 11:25:23.750 MESSAGE Scanner Exception: null ENTRY org.eclipse.cdt.core 4 4 Nov 05, 2004 11:25:23.765 MESSAGE Scanner Exception: null ENTRY org.eclipse.cdt.core 4 4 Nov 05, 2004 11:37:54.864 MESSAGE Failed to index /mysrc/main.cpp *** SESSION Nov 05, 2004 12:36:09.152 ------------------------------------------ *** SESSION Nov 05, 2004 12:39:12.153 ------------------------------------------ *** SESSION Nov 05, 2004 12:44:20.764 ------------------------------------------ *** SESSION Nov 05, 2004 12:51:05.361 ------------------------------------------ ENTRY org.eclipse.cdt.core 4 4 Nov 05, 2004 13:00:50.661 MESSAGE Failed to index /mysrc/main.cpp ~  Are these known problems with version 1 or something else?  Dan

[Altera_Forum]

These problems with not bringing up source for a break point seemed to be solved by deleting the debug configuration then recreating it. So from the IDE tools->debug... then select the projects debug configuration and hit delete. Recreate it again and things seem to work again. 

 Another interesting note is that in order to debug code that is in a linked in separately built library we had to create a dummy project containing the source code. To do this we created an Advanced C++ Project added in all of the lib source code and then also put the source code path in the debugger path. Both of these actions are needed. If I did not put the source path in the debugger I could set a breakpoint in the editor (the little circle breakpoint icon would show up) but it would not stop. When set up correctly the breakpoint circle icon appears to gain a small wooden stake growing out of it. Only then will the breakpoint actually stop the processor.   Note also, that after adding these projects you may have to close the IDE then reenter to get the breakpoints to work.   There was still another case of a properly setup system not stopping at breakpoints. I've not seen enough data to determine yet if the delete/recreate step was enough to snuff that out. Time will tell...  Dan