• State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 22 subscribers
  • Views 2620 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Source code level debugging doesn't work

Jan Nowak

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

Parents
  • 0 in reply to Jan Nowak

    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.

    Franc

Reply
  • 0 in reply to Jan Nowak

    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.

    Franc

Children
No data