Crash

[GoogleCodeExporter]

What steps will reproduce the problem?
1. run xdelta -B 16384 -s filea fileb fileb.xd

What is the expected output? What do you see instead?
Expected: normal operation.
Instead: Crash (windows message box: xdelta has encountered a problem and 
needs to be closed ...)

What version of the product are you using? On what operating system?
3.0k windows xp pro

Please provide any additional information below.
filea ~700mb fileb a bit larger.

Original issue reported on code.google.com by H.Re...@gmail.com on 13 Jan 2007 at 11:13

[GoogleCodeExporter]

Does it run without the "-B 16384" argument? If you run with -vv, what output 
do you
see before the crash? Thanks!

Original comment by josh.mac...@gmail.com on 13 Jan 2007 at 11:33

• Changed state: Accepted

[GoogleCodeExporter]

yes, it works fine with the defaults.
with -vv output as followes:

test1:

xdelta3: input buffer size: 262144
xdelta3: source window size: 16384
xdelta3: source block size: 0
xdelta3: source file: x:\folder\filename.ext: 366186496 bytes

test2: 

xdelta3: input buffer size: 262144
xdelta3: source window size: 16384
xdelta3: source block size: 0
xdelta3: source file: x:\folder\filename.ext: 728109056 bytes

Original comment by HellRe...@gmail.com on 14 Jan 2007 at 1:44

[GoogleCodeExporter]

there is a division-by-zero shortly after it prints "source block size: 0". the
setting of -B is too small. I'm fixing this up and will make some notes with 
the next
release. thanks!

Original comment by josh.mac...@gmail.com on 14 Jan 2007 at 6:16

[GoogleCodeExporter]

Release 3.0l fixes this to allow -B from 16KB to 16MB. I've updated the wiki.
http://code.google.com/p/xdelta/wiki/TuningMemoryBudget

Original comment by dotdotis...@gmail.com on 16 Jan 2007 at 3:10

[GoogleCodeExporter]

Original comment by dotdotis...@gmail.com on 16 Jan 2007 at 3:11

• Changed state: Fixed