flat assembler
Message board for the users of flat assembler.
Index
> Main > Disassembler, debugger, etc... |
Author |
|
r22 23 Feb 2005, 04:51
That would be very convenient. A lot of the good disassemblers like IDApro make you buy them.
|
|||
23 Feb 2005, 04:51 |
|
mike.dld 23 Feb 2005, 06:34
Some time ago I was writing disassembler plug-in for FAR (in FASM, for 16-bit code only) but haven't finished it and it may not be useful... Maybe later, who knows... It's definitely a good idea especially because I've accustomed to FASM syntax and everything else is just confusing me.
|
|||
23 Feb 2005, 06:34 |
|
f0dder 23 Feb 2005, 12:58
|
|||
23 Feb 2005, 12:58 |
|
iklin 23 Feb 2005, 17:57
Hex-viewer/disassembler I know -
HIEW - http://webhost.kemtel.ru/~sen/ It's shareware. Hex-viewer/diassembler which understand 64-bit code - BIEW - http://biew.sourceforge.net/ It's freeware. There are no fasm syntax but this is not so important. I use this utils every day. |
|||
23 Feb 2005, 17:57 |
|
Juras 23 Feb 2005, 21:08
ndisasm utility accompanying nasm is very good and almost the same as FASM's syntax.
for nice debugging FASM must include DEBUG information into the final EXE, like symbol names and their addresses and line numbers and source file names. |
|||
23 Feb 2005, 21:08 |
|
Tommy 23 Feb 2005, 21:41
Quote: for nice debugging FASM must include DEBUG information into the final EXE, like symbol names and their addresses and line numbers and source file names. |
|||
23 Feb 2005, 21:41 |
|
ronware 23 Feb 2005, 23:21
Tommy wrote:
Please....? |
|||
23 Feb 2005, 23:21 |
|
THEWizardGenius 24 Feb 2005, 17:21
Remember, one of the main principles upon which FASM is based is that it assembles ONLY what is in the code- it will not append anything else, except of course EXE headers, etc. However, perhaps a directive, such as "incdebug" or something like that, used in the source... But I really only need a simple disassembler and/or debugger that maybe makes up line labels based on their position in source or by their context (for example, if the position is JMP'd to by a short JMP that is near by, the label would be output to the ASM file as a local label; if no nearby JMP's are used, or if all JMP's referencing that position are FAR, then it would not be local). This might be pretty complex. I suppose FASM syntax isn't the MOST important thing, but it is pretty high on my list... this is exactly what I mean:
Quote: It's definitely a good idea especially because I've accustomed to FASM syntax and everything else is just confusing me. _________________ FASM Rules! OS Dev is fun! Pepsi tastes nasty! Some ants toot! It's over! |
|||
24 Feb 2005, 17:21 |
|
f0dder 24 Feb 2005, 17:23
Well, you could always assemble to coff format and use a linker that generates debug info?
|
|||
24 Feb 2005, 17:23 |
|
THEWizardGenius 24 Feb 2005, 21:33
I don't use Object files, ever, I prefer to use plain binary or if I have to, EXE. But I understand what you mean. Besides, that would be a two-step solution, and why use a two-step solution if you can use a one-step solution
_________________ FASM Rules! OS Dev is fun! Pepsi tastes nasty! Some ants toot! It's over! |
|||
24 Feb 2005, 21:33 |
|
iklin 25 Feb 2005, 15:16
THEWizardGenius wrote: I suppose FASM syntax isn't the MOST important thing, but it is pretty high on my list... Well... Why you can't write your own disasm with fasm syntax? It's not so simple but not so hard. Some times ago I think about it but I have not enough time. |
|||
25 Feb 2005, 15:16 |
|
< Last Thread | Next Thread > |
Forum Rules:
|
Copyright © 1999-2024, Tomasz Grysztar. Also on GitHub, YouTube.
Website powered by rwasa.