Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!zardoz.cpd.com!dhw68k!felix!asylvain@felix.UUCP
From: asylvain@felix.UUCP (Alvin "the Chipmunk" Sylvain)
Newsgroups: comp.lang.c
Subject: Re: Do you trust the "indent" program?
Message-ID: <155337@felix.UUCP>
Date: 3 Jan 91 23:11:36 GMT
References: <12184@sybase.sybase.com> <256@ptcburp.ptcbu.oz.au> <5971@stpstn.UUCP>
Sender: daemon@felix.UUCP
Reply-To: asylvain@felix.UUCP (Alvin "the Chipmunk" Sylvain)
Organization: Foundation for the Advancement of Chipmunks
Lines: 25

In article <5971@stpstn.UUCP> lerman@stpstn.UUCP (Ken Lerman) writes:
> In article <256@ptcburp.ptcbu.oz.au> rick@ptcburp.ptcbu.oz.au (Rick Stevenson) writes:
> .....
> .Why don't you run a copy of your src files through indent, recompile,
> .and compare new object files with the old versions? The proof of the
> .pudding...
> 
> I've never been able to compare object successfully.  Object files
> tend to have imbedded line numbers, version numbers, etc. which cause
> them to compare differently.  Is there a utility out there which will
> enable me to determine if the code and data parts of an executable or
> object file are the same?

You should be able to run 'strip' on the object files to remove any
extraneous garbage, including information for debuggers.  Although I
like someone's suggestion of compiling to assembly source with the -S
option much better.  As he pointed out, this not only identifies a
difference, it indicates where it is as well.  (Or at least gives you an
idea, depending on how transmorgrified it becomes with optimization.)
--
asylvain@felix.UUCP (Alvin "the Chipmunk" Sylvain)
========================= Opinions are Mine, Typos belong to /usr/ucb/vi
"We're sorry, but the reality you have dialed is no longer in service.
Please check the value of pi, or see your SysOp for assistance."
UUCP: hplabs!felix!asylvain ============================================