Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!lll-winken!taurus!gate.ready.com!gate.ready.com!mips2.eng.ready.com!boaz
From: boaz@mips2.eng.ready.com (Boaz Kahana)
Newsgroups: comp.sys.mips
Subject: Re: li.s,li.d
Message-ID: <1991Apr2.170159.209@ready.eng.ready.com>
Date: 2 Apr 91 17:01:59 GMT
References: <1991Apr1.182811.28382@aero.org>
Sender: news@ready.eng.ready.com (Usenet Administrator)
Reply-To: boaz@mips2.eng.ready.com (Boaz Kahana)
Organization: Ready Systems
Lines: 20

In article <1991Apr1.182811.28382@aero.org>, jordan@aero.org (Larry M.
Jordan) writes:
> 
> 
> Also, (and this may be the solution to my question) is
> there a disassembler for the .o files?  The .s files, I'm
> afraid, hide too much of what is going on--I really want to
> know what machine instructions are generated.
> 

If you are developing a code for the MIPS workstation you can examine the 
assemley code by using dbx (after compiling  with -g flag) . 
Disassembley  in DBX is done by <address>/<number>i
 Meaning disassemble <number>  instruction starting at <address>.


Boaz Kahana
Ready Systems 
470 Potrero Ave. Sunnyvale CA 94086
boaz@mips2.eng.ready.com  (408) 522-7392