VCDIFF print command errors (3.x, Windows-specific)

[GoogleCodeExporter]

What steps will reproduce the problem?
1. run xdelta printhdrs filename.xd3
2. run xdelta printdelta filename.xd3
3.

What is the expected output? What do you see instead?
Expected: delta/headers information
Instead: the error 'xdelta3: file open failed: write: /dev/stdout: The 
system cannot find the path specified.' 
shows up shortly/immediatly after xdelta begins outputing information 
about the VCDIFF addr section.

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

Please provide any additional information below.
xdelta seems to expect an output file parameter and is satisfied with any 
such provided, even though the file isn't used (but is created).

on an aside, is there a reason the original path+filenames used to create 
the delta file is preserved in the header ?

Original issue reported on code.google.com by H.Re...@gmail.com on 19 Jan 2007 at 10:51

[GoogleCodeExporter]

I couldn't reproduce this.  The first part of your report, "file open failed",
doesn't happen for me. I can print deltas on my Windows machine, which is also
Windows XP Professional. Not sure how to procceed.

The print commands work for me since version 3.0j, 3.0i would crash.

There is an irregularity with the print commands, which you've noticed. They 
print to
stdout regardless of whether you pass an output filename on the command-line. 
The
reason for this is somewhat lame, and I could either fix it correctly (so that 
print
commands use the same output discipline as the rest of the command-line 
program, this
requires changing from fprintf() to something else) or cover up the problem a 
little
better (so you can't specify an output file to print commands).

Original comment by dotdotis...@gmail.com on 20 Jan 2007 at 7:51

• Changed state: Accepted

[GoogleCodeExporter]

i suppose if you step through the program you could actualy see which file its 
trying to open, possibly its one of the files used in the creation of the delta 
file 
even though it stops complaining when an output file is specified.

Original comment by H.Re...@gmail.com on 21 Jan 2007 at 8:50

[GoogleCodeExporter]

It's trying to open /dev/stdout, I'm just not sure why. I'll take another look.

Original comment by josh.mac...@gmail.com on 21 Jan 2007 at 10:06

[GoogleCodeExporter]

I stepped through this command, "xdelta3 printdelta file.xd3", on both Windows 
and
Linux. In both cases, it only opens the input file "file.xd3", no output file. 
There
must be something else happening. I'm sorry I can't reproduce this.

Longer term, I would like to fix the irregularity noted above, so that 
printdelta can
use the optional output file syntax.

Original comment by dotdotis...@gmail.com on 21 Jan 2007 at 9:01

• Changed state: Started

[GoogleCodeExporter]

well, in case theres something different in our default configurations heres 
the 
output for xdelta config:

VERSION=3.0l
EXTERNAL_COMPRESSION=0
GENERIC_ENCODE_TABLES=0
GENERIC_ENCODE_TABLES_COMPUTE=0
REGRESSION_TEST=1
SECONDARY_DJW=1
SECONDARY_FGK=1
VCDIFF_TOOLS=1
XD3_ALLOCSIZE=16384
XD3_DEBUG=0
XD3_DEFAULT_CKSUM_SIZE=16384
XD3_DEFAULT_IOPT_SIZE=4096
XD3_DEFAULT_SPREVSZ=65536
XD3_DEFAULT_SRCWINSZ=67108864
XD3_DEFAULT_WINSIZE=262144
XD3_ENCODER=1
XD3_HARDMAXWINSIZE=16777216
XD3_NODECOMPRESSSIZE=16777216
XD3_USE_LARGEFILE64=1
XD3_POSIX=0
XD3_STDIO=0
XD3_WIN32=1

also in case its relevant my delta files are usualy created for large files 
from 350-
800MB 

Original comment by H.Re...@gmail.com on 22 Jan 2007 at 6:32

[GoogleCodeExporter]

Original comment by josh.mac...@gmail.com on 2 Feb 2007 at 6:41

[GoogleCodeExporter]

Original comment by josh.mac...@gmail.com on 2 Feb 2007 at 8:51

• Changed title: xdelta3 print command errors (Windows)

[GoogleCodeExporter]

Original comment by josh.mac...@gmail.com on 2 Feb 2007 at 7:53

• Changed title: VCDIFF print command errors (3.x, Windows-specific)
• Changed state: Accepted

[GoogleCodeExporter]

I could never reproduce this problem, but I've rewritten the code to fix the
"irregularity" mentioned above in SVN 112. This will appear in the next 
release. 

Xdelta3 print commands now use the same output-file discipline as the rest of 
the
command-line, so "xdelta3 printdelta input output" prints to the output file.  
As
before, "xdelta3 printdelta input" prints to stdout. Xdelta3 should not try to 
open
/dev/stdout, in any case -- the "/dev/stdout" string is used as the printable
filename, not for actually opening.

Original comment by josh.mac...@gmail.com on 6 Feb 2007 at 6:54

• Changed state: Fixed