Stats

  • Locked Locked
  • Replies 6
  • Subscribers 52
  • Views 24522
  • Members are here 0
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

Path mapping for C Firmware source files when debugging

29erpete

Hi,

i am compiling firmware under Windows transfer the binaries and the sources to Linux to simulate/debug there. The problem is that the paths in the DWARF debug info of the .elf file are the absolute Windows paths as set by the compiler so they are useless under Linux. Is it possible to configure mappings of these paths to the Linux paths when simulating/debugging like with e.g. GDB (https://sourceware.org/gdb/current/onlinedocs/gdb/Source-Path.html#index-set-substitute_002dpath)?

thx,

Peter

Parents

  • The PX4 source code is stored on Github in the px4/firmware repository. I would recommend that you fork this repository and then clone the source to your local computer. The path is stored in the .debug_str section of the binary, as a NUL-terminated string. You can find the section offset from e.g. readelf -S, and edit the string with emacs. Or write a program to do that. If you are still unable to get it right, I would recommend you try an Enterprise Application Development Services who will get it done for you quickly with very little expense.

Reply

  • The PX4 source code is stored on Github in the px4/firmware repository. I would recommend that you fork this repository and then clone the source to your local computer. The path is stored in the .debug_str section of the binary, as a NUL-terminated string. You can find the section offset from e.g. readelf -S, and edit the string with emacs. Or write a program to do that. If you are still unable to get it right, I would recommend you try an Enterprise Application Development Services who will get it done for you quickly with very little expense.

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.