Re: Comparing two EXEs
- From: "Bob" <rcf2@xxxxxxxxx>
- Date: 6 Jul 2005 12:01:02 -0700
That looks promising. TDump has enough options to keep them (QA) busy
thats for sure! :) For some reason they are not happy just seeing that
no actual code has changed. They are paranoid and think that maybe the
compiler has a "glitch" and wont produce the same code everytime...
AlexR wrote:
>
> "Bob" <rcf2@xxxxxxxxx> wrote in message
> news:42cbff76$1@xxxxxxxxxxxxxxxxxxxxxxxxx
> > I know this is slightly technical, but I couldn't decide which
> > group to drop it in.
> >
> > When we make builds of our products, our QA department wants to
> > check the executables to ensure that the ones that were not
> > supposed to change in fact did not change. So they do a byte
> > compare of the new release with the last release. Unfortunately,
> > when we build, we recompile all EXEs. There must be date/time
> > information (or something else?) in the EXEs that make this byte
> > compare fail even if the code did not.
> >
> > My question: Is there a way to compare an EXE to a previous
> > compile of the same EXE and determine if there were actual code
> > changes?
>
> do a TDump of both executables and compare the results, if I remember
> correctly there is an option in TDump to extract the code block,
> that's what you want to compare.
>
> -AlexR
.
- Follow-Ups:
- Re: Comparing two EXEs
- From: Paul Dolen
- Re: Comparing two EXEs
- References:
- Comparing two EXEs
- From: Bob
- Re: Comparing two EXEs
- From: AlexR
- Comparing two EXEs
- Prev by Date: Re: Freedom!
- Next by Date: Re: Freedom!
- Previous by thread: Re: Comparing two EXEs
- Next by thread: Re: Comparing two EXEs
- Index(es):
Relevant Pages
|