aboutsummaryrefslogtreecommitdiff
path: root/tests/files/README
diff options
context:
space:
mode:
authorLasse Collin <lasse.collin@tukaani.org>2008-01-18 20:13:00 +0200
committerLasse Collin <lasse.collin@tukaani.org>2008-01-18 20:13:00 +0200
commit0ae3208db94585eb8294b97ded387de0a3a07646 (patch)
tree4c5ed6d08186edffa101719fe8321aa3faacd017 /tests/files/README
parentFix LZMA_SYNC_FLUSH handling in LZ and LZMA encoders. (diff)
downloadxz-0ae3208db94585eb8294b97ded387de0a3a07646.tar.xz
Added test files to test usage of flush marker in LZMA.
Diffstat (limited to 'tests/files/README')
-rw-r--r--tests/files/README12
1 files changed, 12 insertions, 0 deletions
diff --git a/tests/files/README b/tests/files/README
index e8f4160e..42742629 100644
--- a/tests/files/README
+++ b/tests/files/README
@@ -70,6 +70,12 @@
good-single-delta-lzma.tiff.lzma is an image file that compresses
better with Delta+LZMA than with plain LZMA.
+ good-single-lzma-flush_1.lzma has a flush marker in the middle of
+ the file, and no EOPM.
+
+ good-single-lzma-flush_2.lzma has a flush marker in the middle of
+ the file and just before EOPM.
+
2.2. Bad Files
@@ -115,6 +121,12 @@
but it seemed to be a bad idea since it would increase worst-case CPU
usage.
+ bad-single-lzma-flush_beginning.lzma has flush marker in the beginning
+ of the LZMA data.
+
+ bad-single-lzma-flush_twice.lzma has two flush markers with no data
+ between them.
+
2.3. Malicious Files