Memory Report generation Python/DWARF error

RE: Memory Report generation Python/DWARF error

Vidar Berg — Tue, 19 Mar 2024 15:36:51 GMT

That makes sense. Thank you for the update.

RE: Memory Report generation Python/DWARF error

klaasg — Tue, 19 Mar 2024 14:47:52 GMT

Found the error with the command

$ readelf --debug-dump=info build/zephyr/zephyr.elf | grep -A10 'Compilation Unit @'

Our Zephyr app is compiled with the correct version, 4, but we include an externally compiled library, compiled with DWARF version 5.
Thank you for your help.

RE: Memory Report generation Python/DWARF error

Vidar Berg — Tue, 19 Mar 2024 14:31:28 GMT

Hi,

I think I will need more details about your project to understand why '-gdwarf-4' is not being applied to your build. Are you changing the default build flags in your in your project?

Best regards,

Vidar

RE: Memory Report generation Python/DWARF error

klaasg — Tue, 19 Mar 2024 13:49:15 GMT

Hi,

In VSCode, building and clicking "Memory report" works for zephyr/samples/hello_world.

It doesn't for our app.

I built both tests with the same board, a custom board.

Best regards,

klaasg.

RE: Memory Report generation Python/DWARF error

Vidar Berg — Tue, 19 Mar 2024 12:01:54 GMT

Hi,

I don't recall seeing this error before. It's also strange that DWARF version 5 is selected as it should be set to 4 here: https://github.com/nrfconnect/sdk-zephyr/commit/878edeb6ff190a713910a0e5cb9022704c5934a3 and here: https://github.com/nrfconnect/sdk-zephyr/blob/5c037fe1226d8ae8c8fb964fb60e5de487550d7c/cmake/compiler/gcc/compiler_flags.cmake#L170. Are you receiving this error with the SDK samples?

Best regards,

Vidar