• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Hardware/Software Co-Development, Verification…
  3. Path mapping for C Firmware source files when debugging

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
29erpete over 6 years ago

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

  • Cancel
Parents
  • Will123321
    Will123321 over 5 years ago

    You can multiple-use the -replace path option.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • 29erpete
    29erpete over 5 years ago in reply to Will123321

    Thanks for the reply but as stated previously the paths on the Windows side differ from build to build so without wildcards/regex's this does not work for me.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • 29erpete
    29erpete over 5 years ago in reply to Will123321

    Thanks for the reply but as stated previously the paths on the Windows side differ from build to build so without wildcards/regex's this does not work for me.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information