| User | Post |
MathOnNapkins
Posts: 2060/2189 |
Originally posted by Omega45889
It is very useful for small chunks of code. Much easier to use than a tracer in certain circumstances.
Well technically it is optimal for any contiguous length of code that would work under normal circumstances. The disassembler assume to certain extent that the code you are ripping is correct. Correct... enough. I've seen routines as long as 1000 bytes or more. Didn't choke on those. Actually the real time saver is in the longer routines. Short routines are annoying b/c you have to type in the boundaries more often. |
Omega45889
Posts: 290/335 |
It is very useful for small chunks of code. Much easier to use than a tracer in certain circumstances. |
MathOnNapkins
Posts: 2058/2189 |
It's not designed to disassemble a whole rom. More than likely you would get incorrect results and probably land some jump instructions leading outside of the rom itself- which causes it to stop disassembling and give an error message. But for most purposes it's fast. I could alter that but I don't think it's a good idea. |
HyperLamer
Posts: 5764/8210 |
Nice, but how fast is it? I wrote a VB6 disassembler once (for Gameboy) and it was sloooooow. Took like 10 minutes for a 2MB ROM. |
cpubasic13
Posts: 1234/1346 |
...wow... wow...
This is a very nifty program you got here. Very nice on seeing every instruction from a certain range (and it informing you if it is in the middle of an instruction and to increase the upper address).
Very neat. Simple, yet amazing. Good work.
Really can't seem to see anything bad with it so far, but I will keep looking for any bugs that I may come across... |
MathOnNapkins
Posts: 2057/2189 |
pictures:
yay
so you wanna be a punk?
okay be a punk
<3 <3
more <3
linky : http://mypage.iu.edu/~dwaggone/
Okay finally I have something worthy of releasing. Many suggestions and input have been put into creation of this tool. Some made it in, some didn't. See the suggestions thread for info on that. Though, in the final version I might add in support for recognition of labels or macros b/c I feel pretty confident with what I have now.
If this output doesn't appeal to you I still strongly suggest you download it and give it a try. it supports output to .txt which removes all formatting. And I've included source so at the bare minimum you could hack it if you had the inclincation. There many options, as you can see from the first picture, but there are quite a few that are not shown there. It saves all your preferences on rare opcodes, jump table style (very slick), normal vs. MON settings.
A few of the features are not directly available in the menu or the buttons -
F5- hit to obtain a disassembly with linear override enabled. F3 - is normal disassembly
F6- hit to bring up a dialog for altering opcode rarity. "Load" is if you just want to view the status of the opcode. "Toggle" also loads the opcode's info first, and then toggles its status, so you don't have to worry about altering the wrong flag b/c you didn't load it.
Many more concerns are addressed in the help file (.html) included. The sourcecode is for Visual C++ 6.0 and above, and includes everything you would need to get started.
Report bugs and concerns in this thread. If you have outright suggestions, please use the other thread http://board.acmlm.org/thread.php?id=15848. |
hukka
