m68kdis

KO | EN

gitlite — search

#javascript #hacktoberfest #react #ai #llm #go #deep-learning #linux #docker #nodejs #awesome-list #mcp #ios #open-source

(★ 13)

Ancient but still respectable open source 68k disassembler.

m68kdis 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# `m68kdis`

## Prelude
_This software was not originally made by me._ It was originally written in
1994 by one Christopher G. Phillips. AFAICT, it was originally submitted
to Dr. Dobb's Journal [in 1995](http://www.drdobbs.com/cug-new-releases/184403047?pgno=4).
Other than that and some sparse Usenet postings, I have no information on the
original author.

Unlike most non-commercial assemblers, `m68kdis` can automatically infer code
and data in raw binary images. It is also extremely portable being written in
only ANSI C. If that's not your cup of tea, perhaps bindings can be extracted
for interactive use cases? I might even do it at some point :).

After thinking I lost my original copy, and not finding the source on Github,
I decided to upload a fresh copy. On Windows 7, it compiles as-is if `gcc` is
installed, and probably works fine with MSVC as well. I personally downloaded
my copy from the [Raine emulator website](https://raine.1emulation.com/download/dev.html),
and commited a copy that was last lightly modified in 2002.

The manual, converted from `mandoc` into HTML (expect formatting errors),
follows below.

## Manual
<h1 align="center">M68KDIS</h1>

<a href="#NAME">NAME</a> 
<a href="#SYNOPSIS">SYNOPSIS</a> 
<a href="#DESCRIPTION">DESCRIPTION</a> 
<a href="#OPTIONS">OPTIONS</a> 
<a href="#NOTES">NOTES</a> 
<a href="#BUGS">BUGS</a> 
<a href="#SEE ALSO">SEE ALSO</a> 
<a href="#AUTHOR">AUTHOR</a>

<hr>

m68kdis &minus;
disassemble Motorola 68000 family object code

<h2>SYNOPSIS
<a name="SYNOPSIS"></a>
</h2>

m68kdis
[&minus;ddd]
[&minus;a&nbsp;file] [&minus;all[c]]
[&minus;b&nbsp;file] [&minus;bad]
[&minus;f&nbsp;file]
[&minus;i&nbsp;file]
[&minus;j&nbsp;file] [&minus;l]
[&minus;lft] [&minus;n&nbsp;file]
[&minus;ns&nbsp;file]
[&minus;o&nbsp;file] [&minus;odd]
[&minus;pc&nbsp;initialpc]
[&minus;s&nbsp;length]
[&minus;slenp&nbsp;length]
[&minus;sp] file...

<h2>DESCRIPTION
<a name="DESCRIPTION"></a>
</h2>

m68kdis
is a disassembler for the Motorola 68000 family of cpu
chips. The disassembler attempts to discern between the
instruction and data portions of an object code file.

m68kdis
produces output files much like cc(1). When the
&minus;o option is not used, file arguments that end
in .o have output filenames with .s substituted for .o;
otherwise, .s is simply appended.

The output
consists of five columns:

&bull;</td>
<td width="10%"></td>
<td width="78%">

program counter in hexadecimal</td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="1%">

&bull;</td>
<td width="10%"></td>
<td width="78%">

file contents with each byte displayed as two characters
in hexadecimal</td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="1%">

&bull;</td>
<td width="10%"></td>
<td width="78%">

label (if any)</td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="1%">

&bull;</td>
<td width="10%"></td>
<td width="78%">

instruction name</td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="1%">

&bull;</td>
<td width="10%"></td>
<td width="78%">

operands (if any)</td></tr>
</table>

<h2>OPTIONS
<a name="OPTIONS"></a>
</h2>

&minus;ddd</td>
<td width="5%"></td>
<td width="78%">

Specifies the chip and
coprocessors. Valid values for ddd are currently
000, 008, 010, 020, 030,
851, 881, and 882. This option may be
repeated as appropriate. The default is 000 with no
coprocessors. </td></tr>
</table>

&minus;a&nbsp;file

Specifies that file
contains lines of the form
&lsquo;&lsquo;aXXX&nbsp;instruction&minus;string&rsquo;&rsquo;
which specify acceptable A-line opcodes. XXX is in
hexadecimal.

&minus;all[c]

Specifies that only one pass
should be made, outputting the instruction (if any) at each
word boundary. If the c is included, &minus;i,
&minus;j, &minus;n and &minus;ns
options are also processed, and another pass is made to
ensure consistency between instructions.

&minus;b&nbsp;file

Specifies that file
contains program counter values which are taken as locations
in data to be output on a new line. The values should be one
to a line, and of a form acceptable to strtoul() with
base equal to 0.

&minus;bad</td>
<td width="5%"></td>
<td width="78%">

Specifies that lines should be printed to standard error
that specify which data caused a potential instruction to be
made invalid.</td></tr>
</table>

&minus;f&nbsp;file

Specifies that file
contains lines of the form
&lsquo;&lsquo;fXXX&nbsp;instruction&minus;string&rsquo;&rsquo;
which specify acceptable F-line opcodes. XXX is in
hexadecimal.

&minus;i&nbsp;file

Specifies that file
contains program counter values which are, if possible, to
be taken as locations of valid instructions. The values
should be one to a line, and of a form acceptable to
strtoul() with base equal to 0.

&minus;j&nbsp;file

Specifies that file
contains A-line and F-line opcodes which are unconditional
jumps and therefore do not need to be followed by a valid
instruction. The values should be one to a line, and of a
form acceptable to strtoul() with base equal to
0.

&minus;l</td>
<td width="5%"></td>
<td width="78%">

Specifies that output should be in lower-case.
(Exception: Label references retain an upper-case
&lsquo;&lsquo;L&rsquo;&rsquo;.) </td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="6%">

&minus;lft</td>
<td width="5%"></td>
<td width="78%">

Specifies that instructions that &lsquo;&lsquo;fall
through&rsquo;&rsquo; to a LINK instruction should be
considered valid. By default, these instructions are
considered invalid.</td></tr>
</table>

&minus;n&nbsp;file

Specifies that file
contains program counter values which are to be taken as
locations of data. The values should be one to a line, and
of a form acceptable to strtoul() with base equal to
0.

&minus;ns&nbsp;file

Specifies that file
contains program counter values which are to be taken as
locations at which instructions do not begin. The words at
these locations may, however, be extension words of
instructions. The values should be one to a line, and of a
form acceptable to strtoul() with base equal to
0.

&minus;o&nbsp;file

Specifies the output file. Only
one file to be disassembled may be given when this option is
used.

&minus;odd</td>
<td width="5%"></td>
<td width="78%">

Specifies that instructions may begin at odd offsets.
This can be useful when code to be disassembled is not
stripped out of an object file. In particular, this option
is often needed when disassembling an intact Macintosh
resource fork.</td></tr>
</table>

&minus;pc&nbsp;initialpc

Specifies that initialpc
be taken as the program counter value for the start of the
object code. The default is 0.

&minus;s&nbsp;length

Specifies that data contain at
least length consecutive printable characters to be
output as a string. The minimum value for length is
2; the default is 5.

&minus;slenp&nbsp;length

Specifies that strings should
print out no more than length characters per output
line. The minimum value for length is 10; the default
is 30.

&minus;sp</td>
<td width="7%"></td>
<td width="78%">

Specifies that register A7 should be output as SP,
except in MOVEM instructions.</td></tr>
</table>

<h2>NOTES
<a name="NOTES"></a>
</h2>

The output is
based on Motorola syntax.

Immediate
values are sometimes also output in hexadecimal after an
intervening !.

The following
procedure is used to filter out the data from the
instructions:

&bull;</td>
<td width="10%"></td>
<td width="78%">

An initial pass is made
determining at which file offsets potential instructions
exist and the sizes of those instructions including
operands. </td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="1%">

&bull;</td>
<td width="10%"></td>
<td width="78%">

File offsets specified by the user as being data are
processed. </td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="1%">

&bull;</td>
<td width="10%"></td>
<td width="78%">

File offsets specified by the user as not starting
instructions are processed.</td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="1%">

&bull;</td>
<td width="10%"></td>
<td width="78%">

File offsets specified by the user as being instructions
are processed.</td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="1%">

&bull;</td>
<td width="10%"></td>
<td width="78%">

Potential instructions which reference data as
instructions are changed to data. (This step is repeated
after each of the remaining steps.)</td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="1%">

&bull;</td>
<td width="10%"></td>
<td width="78%">

LINK instructions which are referenced by BSR and JSR
instructions are accepted as final instructions. (A final
instruction is one that is included in the final
output.) </td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="1%">

&bull;</td>
<td width="10%"></td>
<td width="78%">

Remaining LINK instructions are accepted as final
instructions. </td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="1%">

&bull;</td>
<td width="10%"></td>
<td width="78%">

Branching and jumping instructions that reference final
instructions and are not potential extension words of
floating-point instructions are accepted as final
instructions. </td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="1%">

&bull;</td>
<td width="10%"></td>
<td width="78%">

Remaining branching and jumping that are not extension
words of potential floating-point instructions and returning
instructions are accepted as final instructions.</td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="1%">

&bull;</td>
<td width="10%"></td>
<td width="78%">

Overlapping instructions are selected by minimizing the
amount of data.</td></tr>
</table>

You will
probably need 16-bit shorts and 32-bit
ints.

Since
m68kdis uses the imperfect procedure given in the
NOTES , errors may result in the
instruction/data determination. When problems are suspected,
the &minus;badX option can be used to
determine why instructions get interpreted as data. You can
then use the &minus;i, &minus;ns, and
&minus;n options, as appropriate.

Two unusual
conditions checked for should be mentioned. Sometimes the
decision to designate an instruction as a final instruction
is later contradicted and the instruction is changed to
data. In general, the instruction causing the contradiction
should be regarded as data via the &minus;ns option.
Also, sometimes it is reported that there is an
&lsquo;&lsquo;overlap&rsquo;&rsquo; at a certain offset.
This is because m68kdis is unsure if the best
selection of two possible instructions which overlap each
other was made. A quick inspection of the output at this
offset should clear this up. Messages for these conditions
are printed to standard error.

1.</td>
<td width="8%"></td>
<td width="78%">

Motorola: M68000 8/16/32 Bit
Microprocessors: Programmer&rsquo;s Reference Manual,
5th ed., Prentice-Hall, Englewood Cliffs, NJ, 1986.</td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">

2.</td>
<td width="8%"></td>
<td width="78%">

Motorola: M68030: Enhanced 32-Bit Microprocessor
User&rsquo;s Manual, 2nd ed., Prentice-Hall, Englewood
Cliffs, NJ, 1989.</td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">

3.</td>
<td width="8%"></td>
<td width="78%">

Motorola: M68851: Paged Memory Management Unit
User&rsquo;s Manual, 2nd ed., Prentice-Hall, Englewood
Cliffs, NJ, 1989.</td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">

4.</td>
<td width="8%"></td>
<td width="78%">

Motorola: M68881/MC68882: Floating-Point Coprocessor
User&rsquo;s Manual, 2nd ed., Prentice-Hall, Englewood
Cliffs, NJ, 1989.</td></tr>
</table>

<h2>AUTHOR
<a name="AUTHOR"></a>
</h2>

Christopher G.
Phillips 
 Christopher_Phillips@pe.utexas.edu
<hr>

m68kdis

m68kdis 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

m68kdis

m68kdis 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README