[LukeK]

Thanks for the update. In an attempt to get around this portability issue, I created a subst a drive to the actual path and included source files from the subst drive into my VisualGDB project. What I found was that after I compiled and connected to the target, I can’t seem to set any breakpoints.

Here’s a dump of the output from the GDB server when using my subst T:

-break-insert -f T:/embedded/rtcd/src/main.cpp:45
&"No source file named T:/embedded/rtcd/src/main.cpp.n"
^done,bkpt={number="3",type="breakpoint",disp="keep",enabled="y",addr="",pending="T:/embedded/rtcd/src/main.cpp:45",times="0",original-location="T:/embedded/rtcd/src/main.cpp:45"}

I then swapped one of the files in the project out (the one containing main) with the same file, but specified from its absolute path and I was able to set breakpoints again.

Here’s a dump of the output from the GDB server when using the absolute path:

info line *0x800262c
&"info line *0x800262cn"
Line 45 of "D:/views/svn/C002/TestProject_SW/embedded/rtcd/src/main.cpp" starts at address 0x800262c  and ends at 0x800264c .

OK

Any ideas on why or what could be causing this problem?

[LukeK]

Hi Ket,

Thanks for your reply. When would we be expecting this next release?

I also have a question regarding include paths. For IntelliSense to work properly, I find myself configuring either the VisualGDB project properties under “IntelliSense includes” or by configuring the VS project include directories. For compiling to work properly, I then find myself replicating all these paths in the flags.mak so the compiler can use these paths too. Is there a way to reference the project variables in the flags.mak so I that I can maintain only one include paths variable?

[Author]

Posts