Open dinkark-dev opened 10 months ago
Just a heads up, please run the autotests locally and follow up until they all succeed. If you add binaries to the corpus, it's up to you to make sure the autotest doesn't fail on those - regardless of the primary purpose of the PR. I, too, had to debug unrelated discrepancies on readelf/dwarfdump, and the library only became better for that.
On Windows it's doable too, but somewhat trickier.
@dinkark-dev : are you working on this?
Yes, I am working on it. However, I am not quite familiar with the .debug_frames or .debug_aranges sections thus it's taking a while.
Hi @dinkark-dev, thanks for your work on this. I've pushed a test binary generated by TI Code Composer Studio for a TMS320 device to https://github.com/driftregion/pyelftools/blob/dinkar/dwarf-v4-debug-types-support/test/testfiles_for_dwarfdump/dwarf_ticcs.elf
It contains DW_FORM_ref_sig8
tags which pyelftools 0.30 does not yet handle.
Adds support for parsing the .debug_types section introduced in DWARF version 4.
Intends to address the issue #193
Changes:
Known issues: When running unit tests with new ELF binaries generated using the IAR EWARM toolchain,
Credits: Builds over .debug_types updates introduced in #265