Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| [20 earlier articles] |
| Re: Help on disassembler/decompilers ch@dce.ie (1990-09-14) |
| Re: Help on disassembler/decompilers kym@bingvaxu.cc.binghamton.edu.cc.binghamton.edu (1990-09-15) |
| Re: Help on disassembler/decompilers roland@ai.mit.edu (1990-09-16) |
| Re: Help on disassembler/decompilers raulmill@usc.edu (1990-09-16) |
| Re: Help on disassembler/decompilers ch@dce.ie (1990-09-18) |
| Re: Help on disassembler/decompilers ctl8588@rigel.tamu.edu (1990-09-18) |
| Re: Help on disassembler/decompilers megatest!djones@decwrl.dec.com (1990-09-18) |
| Re: Help on disassembler/decompilers markh@csd4.csd.uwm.edu (1990-09-19) |
| Re: Help on disassembler/decompilers td@alice.UUCP (1990-09-21) |
| Newsgroups: | comp.compilers |
| From: | megatest!djones@decwrl.dec.com (Dave Jones) |
| Keywords: | disassemble |
| Organization: | Megatest Corporation, San Jose, Ca |
| References: | <1990Sep14.181616.26890@dce.ie> |
| Date: | 18 Sep 90 22:13:42 GMT |
I just wrote a SPARC object-code dumper a couple of days ago. I am as much
interested in the symbol-table and relocation-information as I am in the
instructions, but I never even worried about data intertwined with the
instructions. (It helps that all SPARC instructions begin on 32 bit
boundaries, of course.) I simply have one flag that prints the text segment
as a hex and ascii dump, another that prints it as machine instructions.
Can't run the assembler over the output, but then we're not supposed to do
that are we? It's plenty good for my purposes, which is to inspect machine
code in order to infer undocumented conventions, and to verify that compiled
code is correct.
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.