Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!snorkelwacker!husc6!spdcc!ima!esegue!compilers-sender From: hrubin@l.cc.purdue.edu (Herman Rubin) Newsgroups: comp.compilers Subject: Re: Help on disassembler/decompilers Summary: Disassemblers can be hard to get Keywords: code, assembler, debug Message-ID: <2524@l.cc.purdue.edu> Date: 7 Sep 90 14:25:29 GMT References: Sender: compilers-sender@esegue.segue.boston.ma.us Reply-To: hrubin@l.cc.purdue.edu (Herman Rubin) Organization: Purdue University Statistics Department Lines: 24 Approved: compilers@esegue.segue.boston.ma.us In article , 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) -- Send compilers articles to compilers@esegue.segue.boston.ma.us {ima | spdcc | world}!esegue. Meta-mail to compilers-request@esegue.