#153 Then debugging gdb try to set breakpoints from other project
Hi. I have three projects on workspace with names "asd", "MK40_1_ETV_TD" and "MK40_1_ETV_TD". When I work with one project, for example "MK40_1_ETV_TD" and run debuging (OpenOCD configuration) I have got strange log in GDB console: it tries to set breakpoints from other projects:
528,567 26-break-insert --thread-group i1 -f D:\Eclipse_GCC_ARM_wks\MK40.1test\src\Clk_manager.c\
:135
528,567 27-break-insert --thread-group i1 -f D:\Eclipse_GCC_ARM_wks\MK40.1test\src\Clk_manager.c\
:133
528,567 28-break-insert --thread-group i1 -f D:\Eclipse_GCC_ARM_wks\MK40.1test\src\Clk_manager.c\
:128
528,567 29-break-insert --thread-group i1 -t -f D:\Eclipse_GCC_ARM_wks\asd\main.c:main
and this result to errors next:
528,623 &"No source file named D:\\Eclipse_GCC_ARM_wks\\MK40.1test\\src\\Clk_manager.c.\n"
528,623 26^done,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="<pending>",pending=\
"D:\\Eclipse_GCC_ARM_wks\\MK40.1test\\src\\Clk_manager.c:135",times="0",original-location="D\
:\\Eclipse_GCC_ARM_wks\\MK40.1test\\src\\Clk_manager.c:135"}</pending>
After this debug session works fine, but errors little annoying.
Full log you can found here http://pastebin.com/pTY27Lsd
Maybe this bug is from other system, not from GNU ARM Plugin, but I do not know from where.
Discussion
yes, I confirm the problem, it is from CDT DSF, but I'll try to find a workaround.
I gave it a look, the problem is deep inside CDT DSF, and would require quite some changes to fix. ideally the patch should be done against CDT, otherwise would require duplicating a lot of code here, creating many maintenability problems.