wimlib

wimlib:dump_blobs

  1. Git
  2. lp:wimlib
  3. dump_blobs
Last commit made on 2017-02-06
Get this branch:
git clone -b dump_blobs https://git.launchpad.net/wimlib

Branch merges

Branch information

Name:
dump_blobs
Repository:
lp:wimlib

Recent commits

9f0e4b9... by Eric Biggers

dump blobs

055a749... by Eric Biggers

v1.11.0

cc3e635... by Eric Biggers

examples/compressfile.c: add back colon that got deleted

521d7ce... by Eric Biggers

tagged_items.c: statically verify size of tagged item header

442113f... by Eric Biggers

xattr.h: statically verify size of xattr header

df84fc5... by Eric Biggers

lzx_compress: optimize storing information in lzx_sequence

Pack the literal run length and match length ourselves instead of using
bitfields, and store the actual match length instead of the adjusted
match length. Also make matchlen=0 represent end-of-block, and store
the full main symbol, not just the match header.

831eeaa... by Eric Biggers

Don't generate GUID in wimlib_create_new_wim()

It's not necessary to generate a GUID in wimlib_create_new_wim() because
one is generated later by wimlib_write(), and nothing seems to assume
that a WIMStruct not yet backed by a file has a valid GUID. This saves
a call to get_random_bytes(). Also remove some unnecessary
initializations to 0.

fc50e25... by Eric Biggers

lzx_compress: fix corruption with long literal run

The last round of updates to the LZX compressor made it start being able
to use larger blocks, up to ~100KB. Unfortunately it was overlooked
that this allows literal runs > 65535 bytes while in one place the
length of a literal run was still being stored in a u16. Therefore, on
incompressible input data this could be wrapped around, causing
incorrect compression. Fix this by enlarging the variable.

533c97b... by Eric Biggers

wimappend: support --delta-from option

--delta-from was previously only supported by wimcapture. But it is
trivial to make wimappend support it too, and it could be useful.

57d737c... by Eric Biggers

hc_matchfinder: use well-defined initialization of best_matchptr

The initial value of best_matchptr is not truly used, but since we do
always compute 'in_next - best_matchptr', assign an initial value which
avoids undefined behavior.