System.NullReferenceException: Object reference not set to an instance of an object about oldrod

[0x410c]

i was wrong, there was an ambiguity in opcodes i found, as the opcode handlers of 2 opcodes are exactly same and oldrod assumes end of function when opcode is recieved. thanks, devirtualisation works great! thanks for the aweosme work!

[Washi1337]

Modifications of KoiVM will always result in problems with either the disassembly or recompilation process.

This error stems from a few instructions not being decoded properly. Specifically, it is trying to emulate a CALL instruction. For binaries protected by vanilla KoiVM this should never happen (see InstructionEmulator).

This is indicative of either:

• The config.json is not correctly filled in, causing some instructions to be incorrectly decoded as CALL instructions.
• There are more modifications applied to this KoiVM than simply some opcode remappings, causing CALL instructions to appear as arguments to e.g., indirect jumps.

Double check your cross-references with the opcode handlers and your config.json. I also added some simple safety guards in the latest commit (56fc436, build should appear on AppVeyor soon), that should at least produce some results, and should enable you to use --salvage and --dump-il and/or --dump-cfg to help debugging which of the two hypotheses is the case.

[0x410c]

im mostly sure that the call opcode is correct, i also rechecked, i am sure later is the case as if i even skip the first function there are more changes which deter devirtualisation