Aira Force - an interactive reassembler

[hop]

Originally Posted by hitchhikr

Working, latest Windows version needs freetype.dll (https://github.com/ubawurinna/freetype-windows-binaries).

Thanks again for pointing this out. I forgot to test the packages

New Windows packages have been uploaded, containing all the DLLs.

[hop]

Version 0.7.6 Released

Changelog:
- Add: Recent files list
- Add: Export Disassembly option
- Add: Status window with disassembly, reassembly and diff status
- Add: Relocated Binary Window
- Add: Basic binary patching: edit hex, replace instruction with NOP/RTS
- Improve: Saved options
- Improve: Option to hide ira -A posterior address/code comment
- Improve: Rename label referenced by selected line
- Improve: Goto dialogue tab-completion and history
- Improve: CPU Window: edit registers, flags, display formats
- Improve: Hunks Window displays RELOC32 data
- Fix: Crash when parsing long lines of disassembly
- Fix: Adding manual EQU with disassembly context menu
- Fix: Support paths containing spaces

More information here: https://howprice.itch.io/aira-force/...-now-available

[hitchhikr]

Checked your tool a bit more thoroughly and i think it won't become really useful before it emulates a complete Amiga.

[hop]

Originally Posted by hitchhikr

Checked your tool a bit more thoroughly and i think it won't become really useful before it emulates a complete Amiga.

Thanks for taking the time to try it out. I hope the tool is useful for static analysis in its current state. Dynamic analysis is more of a stretch goal, but I'm having fun seeing how far I can take it.

The WIP build now loads and overlays the system ROM and I'm making some changes to allow code to be executed directly from memory.

The workflow would need a rethink if a full emulator was built in. The project could change as execution progresses: ROM startup, bootblock, loaders etc. it would be an interesting problem to solve.

[hitchhikr]

I'm specifically thinking about periodic running code like interruptions and memory data loading, those are show stoppers.

[!ZAJC!]

Hey, I just got a Ghidra->IRA export tool working. It might be complementary to AIRA, especially as Ghidra's analyzers and decompilers are pretty good at detecting initial code sections, strings, jump tables, etc.

The thread has a poll, I am not sure if it's worth your and my time to release (0BSD open source of course). Let me know..

[hop]

Originally Posted by !ZAJC!

Hey, I just got a Ghidra->IRA export tool working. It might be complementary to AIRA, especially as Ghidra's analyzers and decompilers are pretty good at detecting initial code sections, strings, jump tables, etc.

The thread has a poll, I am not sure if it's worth your and my time to release (0BSD open source of course). Let me know..

Good work. Would be nice for Amiga users to take a Ghidra analysis and convert it to ira format for use on real hardware.

It could also be handy if Ghidra 68k ASM is not consumable by vasm without postprocessing. Maybe you know the answer to this.

I added basic jump table detection to Aira because it's so common. It would be great if Ghidra has a robust implementation.

I must give Ghidra another chance. I spent a few hours with it and couldn't get comfortable with the UI.

[!ZAJC!]

It could also be handy if Ghidra 68k ASM is not consumable by vasm without postprocessing. Maybe you know the answer to this.

Yes, AFAIK, Ghidra cannot output by itself 68k ASM that you can feed to vasm without editing.

Right now, I could not get Ghidra to output 68k assembly that vasm or something like that would consume and produce an object file or exe, without hand massaging.

Instead, I use my IRA export tool, run IRA on the same exe with the genrated cnf and now I have the disassembly that vasm can easily import, I have labels, strings, the right code sections, right hunks, etc!

I added basic jump table detection to Aira because it's so common. It would be great if Ghidra has a robust implementation.

There's a tremendous amount of jump table code and flow analysis.

I must give Ghidra another chance. I spent a few hours with it and couldn't get comfortable with the UI.

Vladimir's video I posted in the thread was an eye opener for me.. the help is pretty good to. But yeah, it was an upward learning curve.

Personally, I feel an Amiga-specific tool like AIRA can (eventually) outperform Ghidra and in the least you'd want to know what it can do to get some inspiration. Plus Ghidra is open source and liberally licensed, so no fear if you just want to "steal" some ideas