1 .TH NDISASM 1 "The Netwide Assembler Project"
3 ndisasm \- the Netwide Disassembler \- 80x86 binary file disassembler
35 command generates a disassembly listing of the binary file
37 and directs it to stdout.
43 to exit immediately, after giving a summary of its invocation
49 to exit immediately, after displaying its version number.
52 Specifies the notional load address for the file. This option causes
54 to get the addresses it lists down the left hand margin, and the
55 target addresses of PC-relative jumps and calls, right.
58 Manually specifies a synchronisation address, such that
60 will not output any machine instruction which encompasses bytes on
61 both sides of the address. Hence the instruction which
63 at that address will be correctly disassembled.
66 Specifies a number of bytes to discard from the beginning of the
67 file before starting disassembly. This does not count towards the
68 calculation of the disassembly offset: the first
70 instruction will be shown starting at the given load address.
72 .BI \-k " offset,length"
75 bytes, starting from disassembly offset
77 should be skipped over without generating any output. The skipped
78 bytes still count towards the calculation of the disassembly offset.
81 Enables automatic (or intelligent) sync mode, in which
83 will attempt to guess where synchronisation should be performed, by
84 means of examining the target addresses of the relative jumps and
85 calls it disassembles.
88 Specifies either 16-bit or 32-bit mode. The default is 16-bit mode.
91 Specifies 32-bit mode, more compactly than using `-b 32'.
96 only disassembles binary files: it has no understanding of the
97 header information present in object or executable files. If you
98 want to disassemble an object file, you should probably be using
99 .BR objdump "(" 1 ")."
101 Auto-sync mode won't necessarily cure all your synchronisation
102 problems: a sync marker can only be placed automatically if a jump
103 or call instruction is found to refer to it
106 actually disassembles that part of the code. Also, if spurious jumps
107 or calls result from disassembling non-machine-code data, sync
108 markers may get placed in strange places. Feel free to turn
109 auto-sync off and go back to doing it manually if necessary.
112 can only keep track of 8192 sync markers internally at once: this is
113 to do with portability, since DOS machines don't take kindly to more
114 than 64K being allocated at a time.
117 .BR objdump "(" 1 ")."