diff options
author | Yann Collet <cyan@fb.com> | 2018-10-09 21:25:18 (GMT) |
---|---|---|
committer | Yann Collet <cyan@fb.com> | 2018-10-09 21:25:18 (GMT) |
commit | e07a37d712c87b6d47d043b018e4ff86d31996b3 (patch) | |
tree | 6a57d3578cf0827434e23dfc4a77ea5bc90dfe41 /examples/Makefile | |
parent | a963621eb0938a991c417ec75cbfe85bee684fdd (diff) | |
download | lz4-e07a37d712c87b6d47d043b018e4ff86d31996b3.zip lz4-e07a37d712c87b6d47d043b018e4ff86d31996b3.tar.gz lz4-e07a37d712c87b6d47d043b018e4ff86d31996b3.tar.bz2 |
added a test for LZ4F_compressEnd()
which actively tries to make it write out of bound.
For this scenario to be possible,
it's necessary to set dstCapacity < LZ4F_compressBound()
When a compression operation fails,
the CCtx context is left in an undefined state,
therefore compression cannot resume.
As a consequence :
- round trip tests must be aborted, since there is nothing valid to decompress
- most users avoid this situation, by ensuring that dstCapacity >= LZ4F_compressBound()
For these reasons, this use case was poorly tested up to now.
Diffstat (limited to 'examples/Makefile')
0 files changed, 0 insertions, 0 deletions