andr3colonel / ghidra_wasm

Module to load WebAssembly files into ghidra
98 stars 10 forks source link

Hi #1

Closed fcafra closed 4 years ago

fcafra commented 5 years ago

Hi, can this project be run with Ghidra 9.0.4?

I have this error and it seems to not work.

2019-05-27 | 10:55:03 | ERROR | (SleighLanguage) unknown register AF_: C:\Tmp\ghidrawasm-master\data\languages\Webassembly.pspec 2019-05-27 | 10:55:03 | ERROR | (SleighLanguage) unknown register BC: C:\Tmp\ghidrawasm-master\data\languages\Webassembly.pspec 2019-05-27 | 10:55:03 | ERROR | (SleighLanguage) unknown register DE: C:\Tmp\ghidrawasm-master\data\languages\Webassembly.pspec 2019-05-27 | 10:55:03 | ERROR | (SleighLanguage) unknown register HL: C:\Tmp\ghidra_wasm-master\data\languages\Webassembly.pspec 2019-05-27 | 10:55:03 | ERROR | (SleighLanguage) invalid symbol address "ram:0000": C:\Tmp\ghidra_wasm-master\data\languages\Webassembly.pspec 2019-05-27 | 10:55:03 | ERROR | (SleighLanguage) invalid symbol address "ram:0008": C:\Tmp\ghidra_wasm-master\data\languages\Webassembly.pspec 2019-05-27 | 10:55:03 | ERROR | (SleighLanguage) invalid symbol address "ram:0010": C:\Tmp\ghidra_wasm-master\data\languages\Webassembly.pspec 2019-05-27 | 10:55:03 | ERROR | (SleighLanguage) invalid symbol address "ram:0018": C:\Tmp\ghidra_wasm-master\data\languages\Webassembly.pspec 2019-05-27 | 10:55:03 | ERROR | (SleighLanguage) invalid symbol address "ram:0020": C:\Tmp\ghidra_wasm-master\data\languages\Webassembly.pspec 2019-05-27 | 10:55:03 | ERROR | (SleighLanguage) invalid symbol address "ram:0028": C:\Tmp\ghidra_wasm-master\data\languages\Webassembly.pspec 2019-05-27 | 10:55:03 | ERROR | (SleighLanguage) invalid symbol address "ram:0030": C:\Tmp\ghidra_wasm-master\data\languages\Webassembly.pspec 2019-05-27 | 10:55:03 | ERROR | (SleighLanguage) invalid symbol address "ram:0038": C:\Tmp\ghidra_wasm-master\data\languages\Webassembly.pspec

Thanks !

theKidOfArcrania commented 4 years ago

It looks like those "unknown" registers are a relic of the skel pspec stuff that the author just didn't change at all. those errors should be harmless I think. The real error (at least for me) lies I think in a few lines below (where I think there's some memory overlap)

In other words, pretty sure depending on what you're using it for, the code here is (probably) pretty broken

fcafra commented 4 years ago

Thanks for your reply.