Romain Thomas
Romain Thomas
Hi @ba0f3 You should add [patch_imports](https://lief.quarkslab.com/doc/api/python/pe.html#lief.PE.Builder.patch_imports) as well: ```builder.build_imports(True).patch_imports(True)```
As LIEF doesn't use disassembler, the rebuilding of the import table only works if there only ``call`` like on the IAT. Your DLL maybe do some ``lea`` on IAT entries...
Hello @joemikhailgwu Does it still fail if you set `` builder.build_imports(False).patch_imports(False)`` ?
@joemikhailgwu @0xeb I didn't look at this issue yet but if you have a fix I can do a review.
Yes, bindings for Java and Golang would be nice! I don't think I'll have time to handle them so feel free to contribute if you want.
It should not be very complicated. Which feature(s) or patchelf do you need ?
Ack, I think it's strongly related to the underlying version of ``libm.so``
Hi @dzervas Sorry for the late reply. I never tested LIEF on a binary produced by Rust but you can first test if ``parse(...).write(...)`` does not introduce bug.
I think it is related to https://github.com/lief-project/LIEF/issues/369 and https://github.com/lief-project/LIEF/issues/239