From: drew@juliet.cs.colorado.edu (Drew Eckhardt) Subject: Re: 386/486 disassembler? Date: Wed, 12 May 1993 02:17:13 GMT
In article <1993May11.162832.11410@kf8nh.wariat.org> bsa@kf8nh.wariat.org (Brandon S. Allbery) writes:
>In article <C6u4o9.1uo@oea.hobby.nl> dan@oea.hobby.nl (Dan Naas) writes:
>>Harald Koenig (koenig@nova.tat.physik.uni-tuebingen.de) wrote:
>>: I'm locking for a disassembler for Linux executables, object files,
>>: binary blobs of code etc. which outputs hex bytes and mnemonics
>>: (syntax doesn't matter, just human readable).
>>
>> Why do you need a disassembler when you have the source code?????
>
>For locating gcc botches, perhaps?
Nope. If you want to examine compiler output, simply use
cc -S foo.c
You'll get the assembler output from gcc, with all of your symbols
intact, pseudo-ops specifying data size, etc.
-- Boycott USL/Novell for their absurd anti-BSDI lawsuit. | Drew Eckhardt Condemn Colorado for Amendment Two. | drew@cs.Colorado.EDU Use Linux, the fast, flexible, and free 386 unix |