Hello,
I am currently using:
- Ozone 2.56e on Linux with the JLink DLLs 6.30h;
I have an issue where if I am to compile an ELF with DWARF4 instead of DWARF3 (in TI Code Composer Studio), Ozone, either doesn't show debug symbols, either it displays a list of errors of the kind "ElfLib: libdwarf: Line info section too short in func _dwarf_lineno_init (offset, 0x...)".
I thought that it was my compiler having issues until I tried to debug the exact same binary in Eclipse Oxygen with the GNU MCU Eclipse 4.3.2 plugin and a JLink Debug Configuration. In Eclipse all the symbols are loaded and the debugging behaviour is the same as with DWARF3 debug symbols.
This seems to point the problem in Ozone.
I've created an empty TI Code Composer Studio project and compiled to a binary with DWARF4 to reproduce the issue.
Regards,
Alessandro
I am currently using:
- Ozone 2.56e on Linux with the JLink DLLs 6.30h;
I have an issue where if I am to compile an ELF with DWARF4 instead of DWARF3 (in TI Code Composer Studio), Ozone, either doesn't show debug symbols, either it displays a list of errors of the kind "ElfLib: libdwarf: Line info section too short in func _dwarf_lineno_init (offset, 0x...)".
I thought that it was my compiler having issues until I tried to debug the exact same binary in Eclipse Oxygen with the GNU MCU Eclipse 4.3.2 plugin and a JLink Debug Configuration. In Eclipse all the symbols are loaded and the debugging behaviour is the same as with DWARF3 debug symbols.
This seems to point the problem in Ozone.
I've created an empty TI Code Composer Studio project and compiled to a binary with DWARF4 to reproduce the issue.
Regards,
Alessandro