Seva Alekseyev (he/him)

Can you please provide a more high level description of the problem? At the end of the day, what are you trying to learn about these binary files? Because right...

So you have a set of binaries with DWARF and a set of source trees, and you need to know which binary corresponds to which source? Has there been a...

The CPU and the compiler options are trivially parseable from the DWARF info. Find the first CU (compile unit), find the first `DW_TAG_module` DIE, and look at the `DW_AT_producer` attribute....

`bytearray` on Python 2, then. No different from `bytes`, except mutable. They index the same as int arrays, unlike strings.

Locations section parsing would need to be rewritten.

For the paranoid among us, one could make DWARF 5 support explicitly opt-in. Like, a flag that is False by default. That said, I, as a consumer of pyelftools, would...

Look at the `DW_AT_type` attribute. It's a reference to another DIE that describes the datatype. References are usually stored as either a CU-relative offset (`DW_FORM_refX`) or an absolute offset (`DW_FORM_ref_addr`)....

@mmclwd, is this still an issue?

It was not a supported scenario back then, it's still not a supported scenario. What are you trying to do and where is the slowdown exactly?

Usually, *easier* is the opposite of *faster* :) Does your DWARF contain `DW_AT_sibling` attributes? OBTW, is it specifically the loop that takes 30 minutes, or the initial DWARF retrieval (the...