> On 2018-04-02, at 23:11, David Holz <david.holz@grindwork.com> wrote: > > On 03/31/2018 05:00 AM, silverdr@wfmh.org.pl wrote: >> OTOH I am quite a fan of what WhiteFlame did in JS. It is very >> promising one to me. Just "not there yet" as I can't seem to be able >> to load definitions files plus some other things. > > What other things do you want out of it? Importing a simple list of > label definitions would be pretty easy to add. That's like a good starting point. What I'd love to eventually see/use is a tool that allows me to: - drop some files on it - let's start with two only: the binary (or whatever format you already support) and the label definition file - get it/them disassembled (including interactive selection of data types) - navigate through the JMPs/JSRs - add comments as appropriate - automatically mark fragments, which are not accessed directly - save the disassembly to a few popular formats Some things are already there, which is why I find it so promising. > Unfortunately, I'm not going to be adding in .asm export for a while. > There's too many issues to solve for the general case (ie, wildly > varying platform assumption, multiple file overlays, WFDis allowing > names the assembler doesn't like, etc) and I don't want to lock it into > a simpler model that I'd have to tear out later. The main thrust of the > project is to explore mechanical "understanding" of the code, not > necessarily a code modification & reassembly tool... yet. I am not sure I understand this correctly. It is not about using your tool to do modification / reassembly although this is obviously welcome. It is more about "what good is a tool for if one can't really keep/use the outcome of its work?" Yes, you can analyse some short passages this way in order to get understanding but not much beyond that. -- SD! - http://e4aws.silverdr.com/Received on 2018-08-23 17:00:09
Archive generated by hypermail 2.2.0.