| 1 |
|
|
| 2 |
< |
mon, Version 2.2 |
| 3 |
< |
A command-driven file monitor |
| 2 |
> |
mon, Version 3.0 |
| 3 |
> |
A command-driven file monitor |
| 4 |
|
|
| 5 |
< |
Copyright (C) 1997-1999 Christian Bauer, Marc Hellwig |
| 6 |
< |
Freely distributable |
| 5 |
> |
Copyright (C) 1997-2000 Christian Bauer, Marc Hellwig |
| 6 |
> |
GNU binutils disassemblers Copyright (C) 1988, 89, 91, 93, 94, 95, 96, 97, 1998 |
| 7 |
> |
Free Software Foundation, Inc. |
| 8 |
|
|
| 9 |
|
|
| 10 |
|
License |
| 17 |
|
Overview |
| 18 |
|
-------- |
| 19 |
|
|
| 20 |
< |
"mon" is an interactive command-driven file manipulation tool that is inspired |
| 21 |
< |
by the "Amiga Monitor" by Timo Rossi <trossi@jyu.fi>. It has commands and |
| 22 |
< |
features similar to a machine code monitor/debugger, but it is not intended |
| 23 |
< |
to be used for debugging. It doesn't operate on physical or virtual RAM |
| 24 |
< |
locations of a process but rather on a fixed-size (but adjustable) buffer with |
| 25 |
< |
adresses starting at 0. Also, there are no commands to trace code, set |
| 25 |
< |
breakpoints etc. There are, however, built-in PowerPC, 680x0, 6502 and 8080 |
| 26 |
< |
disassemblers. |
| 20 |
> |
"mon" is an interactive command-driven file manipulation tool that is |
| 21 |
> |
inspired by the "Amiga Monitor" by Timo Rossi <trossi@jyu.fi>. It has |
| 22 |
> |
commands and features similar to a machine code monitor/debugger, but it |
| 23 |
> |
lacks any functions for running/tracing code. There are, however, built-in |
| 24 |
> |
PowerPC, 680x0, 80x86, 6502 and 8080 disassemblers. By default, mon operates |
| 25 |
> |
on a fixed-size (but adjustable) memory buffer with adresses starting at 0. |
| 26 |
|
|
| 27 |
|
|
| 28 |
|
Installation |
| 35 |
|
----- |
| 36 |
|
|
| 37 |
|
mon can be started from the Shell or from the Tracker (BeOS), but command line |
| 38 |
< |
history doesn't work when started from the Tracker). If you give no command |
| 39 |
< |
line arguments, mon enters interactive mode. Otherwise, all arguments are |
| 40 |
< |
interpreted and executed as mon commands. The default buffer size is 1MB. |
| 38 |
> |
history doesn't work when started from the Tracker). |
| 39 |
> |
|
| 40 |
> |
Options: |
| 41 |
> |
-m enables symbolic MacOS A-Trap and low memory globals display in the |
| 42 |
> |
680x0 disassembler |
| 43 |
> |
-r makes mon operate in real (virtual) memory space instead of an allocated |
| 44 |
> |
buffer |
| 45 |
> |
|
| 46 |
> |
If no additional command line arguments are given, mon enters interactive |
| 47 |
> |
mode. Otherwise, all remaining arguments are interpreted and executed as mon |
| 48 |
> |
commands. |
| 49 |
> |
|
| 50 |
> |
The default buffer size is 1MB. |
| 51 |
> |
|
| 52 |
|
The mon command prompt looks like this: |
| 53 |
|
|
| 54 |
|
[00000000]-> |
| 176 |
|
of "." is set to the address after the last address displayed. |
| 177 |
|
|
| 178 |
|
|
| 179 |
+ |
b [start [end]] Binary memory dump |
| 180 |
+ |
|
| 181 |
+ |
displays the buffer contents from address "start" to address "end" in a binary |
| 182 |
+ |
format. Entering "b" without arguments is equivalent to "b .". The value of |
| 183 |
+ |
"." is set to the address after the last address displayed. |
| 184 |
+ |
|
| 185 |
+ |
|
| 186 |
|
m [start [end]] Hex/ASCII memory dump |
| 187 |
|
|
| 188 |
|
displays the buffer contents from address "start" to address "end" as hex |
| 197 |
|
set to the address after the last address displayed. |
| 198 |
|
|
| 199 |
|
|
| 200 |
< |
d65 [start [end]] Disassemble 6502 code |
| 200 |
> |
d65 [start [end]] Disassemble 6502 code |
| 201 |
|
|
| 202 |
|
disassembles the buffer contents from address "start" to address "end". |
| 203 |
|
Entering "d65" without arguments is equivalent to "d65 .". The value of |
| 204 |
|
"." is set to the address after the last address displayed. |
| 205 |
|
|
| 206 |
|
|
| 207 |
< |
d68 [start [end]] Disassemble 680x0 code |
| 207 |
> |
d68 [start [end]] Disassemble 680x0 code |
| 208 |
|
|
| 209 |
|
disassembles the buffer contents from address "start" to address "end". |
| 210 |
|
Entering "d68" without arguments is equivalent to "d68 .". The value of |
| 211 |
|
"." is set to the address after the last address displayed. |
| 212 |
|
|
| 213 |
|
|
| 214 |
< |
d80 [start [end]] Disassemble 8080 code |
| 214 |
> |
d80 [start [end]] Disassemble 8080 code |
| 215 |
|
|
| 216 |
|
disassembles the buffer contents from address "start" to address "end". |
| 217 |
|
Entering "d80" without arguments is equivalent to "d80 .". The value of |
| 218 |
|
"." is set to the address after the last address displayed. |
| 219 |
|
|
| 220 |
|
|
| 221 |
< |
d86 [start [end]] Disassemble 80x86 code (very incomplete) |
| 221 |
> |
d86 [start [end]] Disassemble 80x86 code |
| 222 |
|
|
| 223 |
|
disassembles the buffer contents from address "start" to address "end". |
| 224 |
|
Entering "d86" without arguments is equivalent to "d86 .". The value of |
| 340 |
|
clears all currently defined variables. |
| 341 |
|
|
| 342 |
|
|
| 326 |
– |
rmon |
| 327 |
– |
---- |
| 328 |
– |
|
| 329 |
– |
When mon is started as "rmon", it enters "real mode". That is, all memory |
| 330 |
– |
related functions no longer operate on the buffer but on "real" (virtual) |
| 331 |
– |
memory. Unless you are writing Mac emulators, this is probably of not much |
| 332 |
– |
use. :-) |
| 333 |
– |
|
| 334 |
– |
|
| 343 |
|
Examples |
| 344 |
|
-------- |
| 345 |
|
|
