Running Xdelta3 (v309) on Windows XP Home SP3 command line with no arguments results in error message:
"xdelta3: input read failed: (stdin): Not enough storage is available to process this command."
Executing "xdelta3 -h" returns regular help text (which presumably is what should also happen if no arguments are given.) All tests pass. And use of the program to actually do things seems to work fine.
Certainly XP is old and well on the way out so this is likely an ignore bug, but I wanted to mention it in case it was a quick "oh..I see what fixes that" change to the code. This does come up variously on the internet with this guy saying it's a matter or selecting project type (during compiliation I assume):
http://nnish.com/2009/10/31/error-not-enough-storage-is-available-to-process-this-command/
Other sites will indicate it isn't specific to XP and happens to some programs on Vista and Server 2008. Some comments (from 2 sites I saw) discuss the end user modifying their registry instead to modify "IRPStackSize" which doesn't seem like the proper answer to me (and others seem to agree that isn't the answer). A sample link with comments nevertheless is here:
http://blog.rongabriel.com/not-enough-storage-is-available-to-process-this-command/
LIke I said, Xdelta passes tests and seems to otherwise run fine. I just think there is something wrong with the code when arguments are zero which probably isn't a big fix. Maybe pseudocode:
If arguments==0 then assume "xdelta3 -h"
is all that the code needs since that command works?
Running Xdelta3 (v309) on Windows XP Home SP3 command line with no arguments results in error message:
"xdelta3: input read failed: (stdin): Not enough storage is available to process this command."
Executing "xdelta3 -h" returns regular help text (which presumably is what should also happen if no arguments are given.) All tests pass. And use of the program to actually do things seems to work fine.
Certainly XP is old and well on the way out so this is likely an ignore bug, but I wanted to mention it in case it was a quick "oh..I see what fixes that" change to the code. This does come up variously on the internet with this guy saying it's a matter or selecting project type (during compiliation I assume): http://nnish.com/2009/10/31/error-not-enough-storage-is-available-to-process-this-command/
Other sites will indicate it isn't specific to XP and happens to some programs on Vista and Server 2008. Some comments (from 2 sites I saw) discuss the end user modifying their registry instead to modify "IRPStackSize" which doesn't seem like the proper answer to me (and others seem to agree that isn't the answer). A sample link with comments nevertheless is here: http://blog.rongabriel.com/not-enough-storage-is-available-to-process-this-command/
LIke I said, Xdelta passes tests and seems to otherwise run fine. I just think there is something wrong with the code when arguments are zero which probably isn't a big fix. Maybe pseudocode:
is all that the code needs since that command works?