dev747368

seems reasonable, and the PR looks ok. I'll comment in the branch about a few things and we'll go from there.

initial troubleshooting: it looks like these binaries are using a newer option for compressed Elf sections that we don't support yet.

I did a proof-of-concept several years ago that is in no state to be shared or even 'thrown-over-the-wall'. Ryan is partially right in that in some modes the jshell api...

As a follow up to my report, as a test I changed the hash value embedded in the property file to be the bad hex string (sans-leading-zeros) and with that...

I now see that someone has already submitted a PR to fix this. https://github.com/borisbrodski/sevenzipjbinding/pull/34

No progress to report on DWARF 5. There are some changes / improvements in the pipeline improving function parameter / local variable storage.

Could you bake the logical offset magic into a ByteProvider wrapper?

Yeah, it seems a bit too niche to add to BinaryReader itself. I would copy/paste ByteProviderWrapper (about 130 lines of code), and add a setter to change the offset so...

Could you confirm that your Elf binary is a 32 bit file?

Does putting a ```api.start()``` (to start a db transaction) right after ```val api = FlatProgramAPI....```, and then a ```api.end()``` somewhere at the bottom help things out?