Related articles |
---|
Help on disassembler/decompilers wwho@ucdavis.edu (1990-09-06) |
Re: Help on disassembler/decompilers hrubin@l.cc.purdue.edu (1990-09-07) |
Re: Help on disassembler/decompilers pardo@cs.washington.edu (1990-09-07) |
Re: Help on disassembler/decompilers raul@sdnp1.ucsd.edu (1990-09-07) |
Re: Help on disassembler/decompilers seanf@sco.COM (1990-09-09) |
Re: Help on disassembler/decompilers rwallace@vax1.tcd.ie (1990-09-09) |
Re: Help on disassembler/decompilers vu0310@bingvaxu.cc.binghamton.edu.cc.binghamton.ed (1990-09-10) |
Re: Help on disassembler/decompilers hankd@dynamo.ecn.purdue.edu (1990-09-09) |
[21 later articles] |
Newsgroups: | comp.compilers |
From: | hrubin@l.cc.purdue.edu (Herman Rubin) |
Summary: | Disassemblers can be hard to get |
Keywords: | code, assembler, debug |
Organization: | Purdue University Statistics Department |
References: | <HOW.90Sep5173755@sundrops.ucdavis.edu> |
Date: | 7 Sep 90 14:25:29 GMT |
In article <HOW.90Sep5173755@sundrops.ucdavis.edu>, wwho@ucdavis.edu (W. Wilson Ho) writes:
>
> I am looking for any information related to disassembling
> object code into assembly langauge or even higher-level language such
> as C. Would someone please give me pointers to program sources,
> documentation or papers related to this?
...................
> [Turning object code back into assembler is pretty straightforward, and
> every debugger does it. Someone else asked about disassembling into higher
> level languages a little while ago, but I didn't see any responses. -John]
It is not quite that straightforward, and disassemblers can be somewhat
hard to get. Debuggers usually use object code set up specially for
debugging, with certain features available. Some debuggers even require
that the source code be included in such a way that this can be displayed
at debug time. Disassembly frequently is even ambiguous.
--
Herman Rubin, Dept. of Statistics, Purdue Univ., West Lafayette IN47907
Phone: (317)494-6054
hrubin@l.cc.purdue.edu (Internet, bitnet) {purdue,pur-ee}!l.cc!cik(UUCP)
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.