Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Issue #23] Allow larger than 2GB files to be read. #24

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Issue #23] Allow larger than 2GB files to be read. #24

wants to merge 1 commit into from

Commits on Jan 14, 2019

  1. [Issue mendsley#23] Allow larger than 2GB files to be read. 

    `read` and `write` return a signed int, meaning that they can only read
up to 2 billion bytes (2GB) at a time. bsdiff and bspatch were expecting
the entire file to be read (or written, respectively) in a single call
to `read` or `write`, which is only possible if they are less than 2GB
in size. There are also other times in which a single function call
would be inadequate for IO, for instance in the case where a device is
busy. The fix for this was to place the functions in a loop and continue
as long as at least 1 byte was transferred (in or out). If an error, or 0
return value, comes back from the transfer, break out of the loop and
return the total number of bytes that had been transferred up to that
point.

Updated the .gitignore file to ignore vim swap files, as well as the
autoconf (generated) files and the executables.
    @jwkblades
    jwkblades committed Jan 14, 2019
    Configuration menu
    Copy the full SHA
    b1de290 View commit details
    Browse the repository at this point in the history