Community
Participate
Working Groups
Raised in Bug 530377 Comment 3: DSF is sending -break-after commands to GDB even though state is not actually changing. For example: #include <stdio.h> #include <stdlib.h> int main(void) { for (int i = 0; i < 40000; i++) puts("!!!Hello World!!!"); /* prints !!!Hello World!!! */ return EXIT_SUCCESS; } Added breakpoint on puts call with ignore count 10000 and resumed. Execution completed in no time, when I checked the value of 'i', it was around 18000 and even after all breakpoint-modified messages have been appeared in gdb traces console, following keeps on appearing in gdb console. 592,412 48-break-after 1 7877 592,422 48^done 592,422 (gdb) 596,832 49-break-after 1 6219 596,847 49^done 596,847 (gdb) .... ....
We discussed this at a CDT call recently. The plan on this going forward is to simply not update the Platform breakpoint with the current hit count. This looks to probably resolve the issue, but it won't make it into 9.5.
New Gerrit change created: https://git.eclipse.org/r/132637
Gerrit change https://git.eclipse.org/r/132637 was merged to [master]. Commit: http://git.eclipse.org/c/cdt/org.eclipse.cdt.git/commit/?id=3cf0297769e5cfb91823e93ce570120a75fe01ce
CDT now ignores changes to ignore count from GDB. Updated N&N: https://wiki.eclipse.org/CDT/User/NewIn96#Debug