PatchDiff - 3.3.5 to 4.0.3

[Tanaris4]

Anyone having any issues using PatchDiff? Mine has been running for 10 minutes and I'm not sure if it's just not going to work, or seriously needs some time.

Thoughts? (And yes it's mac binaries, Intel, but I doubt that would matter)

[[Pat]]

4.0.3 isn't the next patch, its 4.0.1

[Tanaris4]

thanks for not actually answering the question, I'm using binary 4.0.3.13117

[XTZGZoReX]

It can take a lot of time on some binaries, so have some patience...

Do know, though, that it has some nasty inf. loop bugs that seem to trigger randomly.

[Tanaris4]

Interesting, it's been going for about an hour now (in a virtual machine), might just let it run until tomorrow and see if it finishes. Otherwise I'll have to /cry

Or actually download the source to the plugin + tinker around, would prob. be a better use of my time then trying to find all the functions for OS X again :/

[XTZGZoReX]

An alternative is TurboDiff: Corelabs site

[Tanaris4]

An alternative is TurboDiff: Corelabs site

Thanks I'll try that now, just got home and it was still stuck @ using 50% of my CPU and doing nothing :/

[Nesox]

http://code.google.com/p/binarydiffer/
i use binarydiffer, patchdiff2 decided to stop working.
Just start the executable and the plugins in 2 open idb's and you get a list of matched/unmatched blocks once it's done

[Tanaris4]

Got TurboDiff to work, was SOOOOO happy :-) Sucks having to copy/paste like 32,000 lines tho heh. Might check out BinaryDiffer, in the past I had issues

[caytchen]

Same here, it does finish but will take a good day to do so on a quad. binarydiffer works fine though.