Re: comparing executables

2002-04-03 Thread Terry Lambert
I guess I wonder why the code differs, then? -- Terry [EMAIL PROTECTED] wrote: > > >Compare them without the ELF headers, a section at a time, so > >that the timestamps are irrelevent. > > >From what I recall, there _are_ no timestamps in ELF images, > and compiling the same executable multipl

Re: comparing executables

2002-04-03 Thread Julian Elischer
On Wed, 3 Apr 2002 [EMAIL PROTECTED] wrote: > > >Compare them without the ELF headers, a section at a time, so > >that the timestamps are irrelevent. > > From what I recall, there _are_ no timestamps in ELF images, > and compiling the same executable multiple times locally here > seems to bea

Re: comparing executables

2002-04-03 Thread peter . edwards
>Compare them without the ELF headers, a section at a time, so >that the timestamps are irrelevent. >From what I recall, there _are_ no timestamps in ELF images, and compiling the same executable multiple times locally here seems to bear out the fact: "cmp" on two successive outputs is identical

Re: comparing executables

2002-04-03 Thread Terry Lambert
Compare them without the ELF headers, a section at a time, so that the timestamps are irrelevent. You may also have to throw out the "what" information from the binaries, preemptively... Julian Elischer wrote: > > I have two directories of executables > (actually two entire FreeBSD filesystems)

Re: comparing executables

2002-04-03 Thread Jake Burkholder
Apparently, On Wed, Apr 03, 2002 at 10:01:36PM +0200, Poul-Henning Kamp said words to the effect of; > In message <[EMAIL PROTECTED]>, Ju > lian Elischer writes: > > > > > >On Wed, 3 Apr 2002, Poul-Henning Kamp wrote: > > > >> > >> >How can I find out which binaries have changed? > >> >t

Re: comparing executables

2002-04-03 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Ju lian Elischer writes: > > >On Wed, 3 Apr 2002, Poul-Henning Kamp wrote: > >> >> >How can I find out which binaries have changed? >> >they are all different according to cksum so I assume >> >that there is a timestamp or something in them. >> >Is there a way to c

Re: comparing executables

2002-04-03 Thread Julian Elischer
On Wed, 3 Apr 2002, Poul-Henning Kamp wrote: > > >How can I find out which binaries have changed? > >they are all different according to cksum so I assume > >that there is a timestamp or something in them. > >Is there a way to compare only the text segments? > > You can do wonders with objdum

Re: comparing executables

2002-04-03 Thread Mark Murray
> > >How can I find out which binaries have changed? > >they are all different according to cksum so I assume > >that there is a timestamp or something in them. > >Is there a way to compare only the text segments? > > You can do wonders with objdump(1) and diff. and ident(1). M -- o Mar

Re: comparing executables

2002-04-03 Thread Poul-Henning Kamp
>How can I find out which binaries have changed? >they are all different according to cksum so I assume >that there is a timestamp or something in them. >Is there a way to compare only the text segments? You can do wonders with objdump(1) and diff. -- Poul-Henning Kamp | UNIX since Zilog

comparing executables

2002-04-03 Thread Julian Elischer
I have two directories of executables (actually two entire FreeBSD filesystems) they were both produced from the same checked out trees except that between the two compiles, some patches (unknown) were applied to the sources. How can I find out which binaries have changed? they are all differen