xz.git - XZ Utils

Age	Commit message (Collapse)	Author	Files	Lines
2018-10-26	liblzma: Don't verify header CRC32s if building for fuzz testing.	Lasse Collin	1	-1/+4
	FUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION is #defined when liblzma is being built for fuzz testing. Most fuzzed inputs would normally get rejected because of incorrect CRC32 and the actual header decoding code wouldn't get fuzzed. Disabling CRC32 checks avoids this problem. The fuzzer program must still use LZMA_IGNORE_CHECK flag to disable verification of integrity checks of uncompressed data.
2017-03-30	liblzma: Make lzma_index_decoder_init() visible to other liblzma funcs.	Lasse Collin	1	-5/+5
	This is to allow other functions to use it without going via the public API (lzma_index_decoder()).
2017-03-30	liblzma: Fix handling of memlimit == 0 in lzma_index_decoder().	Lasse Collin	1	-2/+2
	It returned LZMA_PROG_ERROR, which was done to avoid zero as the limit (because it's a special value elsewhere), but using LZMA_PROG_ERROR is simply inconvenient and can cause bugs. The fix/workaround is to treat 0 as if it were 1 byte. It's effectively the same thing. The only weird consequence is that then lzma_memlimit_get() will return 1 even when 0 was specified as the limit. This fixes a very rare corner case in xz --list where a specific memory usage limit and a multi-stream file could print the error message "Internal error (bug)" instead of saying that the memory usage limit is too low.
2016-11-21	liblzma: Avoid multiple definitions of lzma_coder structures.	Lasse Collin	1	-13/+20
	Only one definition was visible in a translation unit. It avoided a few casts and temp variables but seems that this hack doesn't work with link-time optimizations in compilers as it's not C99/C11 compliant. Fixes: http://www.mail-archive.com/xz-devel@tukaani.org/msg00279.html
2012-07-17	liblzma: Make the use of lzma_allocator const-correct.	Lasse Collin	1	-6/+6
	There is a tiny risk of causing breakage: If an application assigns lzma_stream.allocator to a non-const pointer, such code won't compile anymore. I don't know why anyone would do such a thing though, so in practice this shouldn't cause trouble. Thanks to Jan Kratochvil for the patch.
2011-05-17	Add underscores to attributes (__attribute((__foo__))).	Lasse Collin	1	-4/+5

2010-10-21	liblzma: Update the comments in the API headers.	Lasse Collin	1	-0/+1
	Adding support for LZMA_FINISH for Index encoding and decoding needed tiny additions to the relevant .c files too.
2010-01-01	Fix _memconfig() functions.	Lasse Collin	1	-4/+6
	This affects lzma_memusage() and lzma_memlimit_get().
2009-12-31	Revised the Index handling code.	Lasse Collin	1	-4/+8
	This breaks API and ABI but most apps are not affected since most apps don't use this part of the API. You will get a compile error if you are using anything that got broken. Summary of changes: - Ability to store Stream Flags, which are needed for random-access reading in multi-Stream files. - Separate function to set size of Stream Padding. - Iterator structure makes it possible to read the same lzma_index from multiple threads at the same time. - A lot faster code to locate Blocks. - Removed lzma_index_equal() without adding anything to replace it. I don't know what it should do exactly with the new features and what actually needs this function in the first place other than test_index.c, which now has its own code to compare lzma_indexes.
2009-11-25	Index decoder fixes.	Lasse Collin	1	-6/+20
	The Index decoder code didn't perfectly match the API docs, which said that i will be set to point to the decoded Index only after decoding has succeeded. The docs were a bit unclear too. Now the decoder will initially set i to NULL. *i will be set to point to the decoded Index once decoding has succeeded. This simplifies applications too, since it avoids dangling pointers.
2009-04-28	Fixed a crash in liblzma.	Lasse Collin	1	-1/+1
	liblzma tries to avoid useless free()/malloc() pairs in initialization when multiple files are handled using the same lzma_stream. This didn't work with filter chains due to comparison of wrong pointers in lzma_next_coder_init(), making liblzma think that no memory reallocation is needed even when it actually is. Easy way to trigger this bug is to decompress two files with a single xz command. The first file should have e.g. x86+LZMA2 as the filter chain, and the second file just LZMA2.
2009-04-13	Put the interesting parts of XZ Utils into the public domain.	Lasse Collin	1	-10/+3
	Some minor documentation cleanups were made at the same time.
2009-02-02	Modify LZMA_API macro so that it works on Windows with	Lasse Collin	1	-2/+2
	other compilers than MinGW. This may hurt readability of the API headers slightly, but I don't know any better way to do this.
2009-01-20	Add some single-call buffer-to-buffer coding functions.	Lasse Collin	1	-14/+69

2008-12-15	Bunch of liblzma API cleanups and fixes.	Lasse Collin	1	-7/+39

2008-11-19	Oh well, big messy commit again. Some highlights:	Lasse Collin	1	-16/+15
	- Updated to the latest, probably final file format version. - Command line tool reworked to not use threads anymore. Threading will probably go into liblzma anyway. - Memory usage limit is now about 30 % for uncompression and about 90 % for compression. - Progress indicator with --verbose - Simplified --help and full --long-help - Upgraded to the last LGPLv2.1+ getopt_long from gnulib. - Some bug fixes
2008-08-28	Sort of garbage collection commit. :-\| Many things are still	Lasse Collin	1	-11/+3
	broken. API has changed a lot and it will still change a little more here and there. The command line tool doesn't have all the required changes to reflect the API changes, so it's easy to get "internal error" or trigger assertions.
2008-06-18	Update the code to mostly match the new simpler file format	Lasse Collin	1	-0/+252
	specification. Simplify things by removing most of the support for known uncompressed size in most places. There are some miscellaneous changes here and there too. The API of liblzma has got many changes and still some more will be done soon. While most of the code has been updated, some things are not fixed (the command line tool will choke with invalid filter chain, if nothing else). Subblock filter is somewhat broken for now. It will be updated once the encoded format of the Subblock filter has been decided.