Patrick McCarty 2e5b80929c Make revised search algorithm thread safe
In commit 85b1c5345b, I introduced a new "max_len" variable, used by the
search() function to store the maximum match length found in course of
the binary search.

However, I overlooked the fact that the search() function then lost
thread safety, as "max_len" would be shared by all threads of a process
using libbsdiff.

Fix the issue by not using a global variable, instead updating "max_len"
via another pointer, just like the "pos" variable is handled already.

Signed-off-by: Patrick McCarty <patrick.mccarty@intel.com>
2018-06-14 14:46:52 -07:00
2016-02-16 11:57:55 -08:00
2016-02-16 11:57:55 -08:00
2016-02-16 11:57:55 -08:00
2016-11-21 10:50:39 -08:00
2016-02-16 11:57:55 -08:00
2016-02-16 11:57:55 -08:00
2018-02-22 18:04:24 -08:00
2016-02-16 11:57:55 -08:00
2016-02-16 11:57:55 -08:00
2016-02-16 11:57:55 -08:00
2016-02-16 11:57:55 -08:00

This project is a forked version of BSDiff, as taken from the Chromium project
at SVN Revision 122769. See README.chromium for background on its origins.

Significant changes after the fork include:

- Changing the BSDiff file format to support file owner, group, and permission
  information.
- Adding more robust error handling.
- Adding a new program, bsdump, that outputs BSDiff header information.
- Converting the core functionality into a library, libbsdiff, with public API
  functions make_bsdiff_delta() and apply_bsdiff_delta().
S
Description
No description provided
Readme 2.1 MiB
Languages
C 80%
Shell 9.9%
Makefile 4.8%
M4 3.3%
Perl 2%