Yet another "ELF architecture 164 is not supported"

[clark-ja]

TL;DR; I am getting the exact same error message as mentioned in issue #1 but the proposed solution to use the user plugin directory instead of the global one did not help in this instance.

More details:

Here are my partial logs (with irrelevant information such as other core plugin loading etc omitted):

[Core] Loaded native plugin arch_hexagon
...
[BinaryView.ElfView] ELF architecture 164 is not supported
[Default] BinaryView of type 'ELF' failed to initialize!

I have tried symlinking the libarch_hexagon.so into the user plugin directory and also copying it there didn't make a difference.

Furthermore I can see the the hexagon architecture is loaded from the python console, e.g., with hexagon_arch = Architecture["hexagon"] and getting the respective architecture object back.

To compile binja-hexagon I have updated the third party submodules for binaryninja-api (Vector35/binaryninja-api@3ee274ac) and abseil-cpp (abseil/abseil-cpp@3fba335b) and I am using the currently newest binaryninja dev version (4.3.6676-dev Personal).

Can anyone point my in the right direction to a solution for this problem? Is there something I can try or do you need more information?

[clark-ja]

I did find some bugs in the python code in the usage of the v_args decorator of the lark requirement where the arguments children and meta are consequently switched. There has been a documentation update since to clarify the misleading previous documentation. Here is the related commit: lark-parser/lark@35ab586

[clark-ja]

Fixed with PR #21