Here's a new version of Etripator. Your favorite pcengine disassembler. Unfortunately I can't update the M$ Visual C++ project/solution nor the DevCpp project files for the time being. So you'll have to do it yourself or wait a few weeks (months? ).
So... What's new? Not much. Except that there's a new configuration file format supported.
Wave goodbye to the old CSV file (well it's still here via --csv command line) and give a warm welcome to the infamous INI/CFG file
Here's a copy/paste from the README.txt file:
The almighty README.txt wrote:Each section starts with the name of the output file between square brackets. The supported fields are :
type (mandatory) : values are code ,bin_data or inc_data.
'code' is self explanatory.
'inc_data' means that the section is pure data. But it will be output as code directives (.db)
'bin_data' is also for data section. The output file will contain binary data.
bank (mandatory) : bank of the current section. It will be used to compute the file offset of the section if the 'offset' field is missing.
org (mandatory) : program counter location. Just like 'bank', it will be used to compute file offset if there's no 'offset' field.
offset : file offset. This field is useful for CD-ROM disassembly.
size : section size. For code section, a negative (or missing size) means that the disassembly will stop when a RTS or RTI instruction is found. This field is mandatory for data sections.
Etripator's code is now on github: https://github.com/BlockoS/Etripator.
I created a bunch of issues for the next release [here]. So if you have any requests, just create new ones. And maybe consider joining or forking the project
Deadline failed I got lost in the "Make it support multiple plateform" plan.
By the way I was thinking about adding support for disassembling HES files. Anyone interested?
Etripator 0.3 is released (link).
There're no binaries for the moment. I'll post them tomorrow.
So what's new?
Nothing much. Some bugfixes. I added a licence (gpl v3). There's a Makefile for linux/mingw. The magic value for the code section was changed to 0.
By the way, I don't plan to work much on it unless people start to complain (or just use it).
Work on the 1.0 version have officially started.
This version will try to add multi-platform support, smarter configuration via scripts.
There's no deadline yet.
Have you thought about doing a tracer? It's part dissassembler and part cpu emulator. It basically starts from the reset vector, and follows every possible code path it can take. I started writing one many years ago, but it quick quite complex.
That's planed but that will require to conceptualize some stuffs (like register, memory, storage, etc...).
At the moment I'm on the boring stuffs (command line parsing, etc...).