Hi,
I want to proced source code level debugging with my own library (*.libc file). It doesn't work when library project and aplication project are placed together into workspace. There are no problem when I open standalone aplication project. What is the problem? Any suggestion?
Best regards, JN
You need to tell the debugger where your sources for the library are located with the set src= command. This can be done from the command window or from the ini file.
The command syntax is: set src=<path>
Franc
Let me explain this. I have two projects: A library project, and B aplication project. I'm using binary library file (*.libc) into my aplication project. I put this two project together into one workspace, and when I'm debuging library code througt aplication project it doesn't work. But, when I open plain aplication project, I can proceed library source level debugging with no problems(debug info atached to library, "SET SRC=.." in INI file as DEBUGGER command). Problem is only when I'm trying to use this two projects together in one workspace. Maybe you can chack this by your own? Any idea where is the problem?
Regards, J.N.
Jan,
that is exactly what I'm telling you. Here is an example from the RL-ARM. The SD_File example has included the File System binary library file FS_ARM_L.lib. This library was build as a separate project. You can debug the SD_File example at source level but not the included library.
However if you tell the debugger where the sources for the library FS_ARM_L.lib are located, then the debugging for the the binary lib file, which is included into the application project will also work. And then instead of single stepping through the library in assembly instructions, it single steps in the library source.
With set src=<path> command, the debugger additionally searches the specified <path> for the source files.
Of course this library has to be built with the debug information, othervise this is still not possible.