Re:Disassembly Required
by khedoros1 on Friday December 23, 2016 @08:53PM
(#13248204)
This is better than the last online disassembler that I tried.
One benefit over the free IDA: Support for a ton of architectures.
Oddly, it detected the format of a DOS binary that I fed it, but decided that it couldn't find the code entry point (which is encoded trivially in the header of the binary format).
I also gave it a PocketPC ARM binary. It identified a lot of functions, but didn't say which one was the code entry point (at least, not that I saw). I also don't think it identified any of the Win CE system calls.
Re:Disassembly Required
by cranklin on Friday December 23, 2016 @11:18PM
(#13248563)
if your source code is compiled without symbols, or if your elf executable is missing the section headers, or you've run strip, the disassembler will not give you the function names or the variable names.
Re:Disassembly Required
by wslh on Saturday December 24, 2016 @08:03AM
(#13249643)
But, can you debug with this disassembler? Silence... 80% of my company work involves reverse engineering in Windows and we don't find this tool useful for real work.
https://android.fallible.co
or see which apps people are playing with:
https://android.fallible.co/recent
One benefit over the free IDA: Support for a ton of architectures.
Oddly, it detected the format of a DOS binary that I fed it, but decided that it couldn't find the code entry point (which is encoded trivially in the header of the binary format).
I also gave it a PocketPC ARM binary. It identified a lot of functions, but didn't say which one was the code entry point (at least, not that I saw). I also don't think it identified any of the Win CE system calls.
Certainly fine for getting started though.