- 07 6月, 2022 1 次提交
-
-
由 shuaiyutao 提交于
Change-Id: I156b5b16bbd93817ed1f1ad975c1a1dbdfb520f0 Signed-off-by: Nshuaiyutao <shuaiyutao1@huawei.com>
-
- 11 3月, 2021 1 次提交
-
-
由 mamingshuai 提交于
-
- 09 9月, 2020 1 次提交
-
-
由 wenjun 提交于
-
- 16 1月, 2017 1 次提交
-
-
由 Mark Adler 提交于
-
- 02 1月, 2017 1 次提交
-
-
由 Mark Adler 提交于
-
- 01 1月, 2017 1 次提交
-
-
由 Mark Adler 提交于
-
- 04 12月, 2016 2 次提交
-
-
由 Mark Adler 提交于
Normally these are set to size_t and ssize_t. But if they do not exist, then they are set to the smallest integer type that can contain a pointer. size_t is unsigned and ssize_t is signed.
-
由 Mark Adler 提交于
In some cases the return values did not match the documentation, or the documentation did not document all of the return values. gzprintf() now consistently returns negative values on error, which matches the behavior of the stdio fprintf() function.
-
- 30 1月, 2016 1 次提交
-
-
由 Mark Adler 提交于
-
- 02 8月, 2015 1 次提交
-
-
由 Mark Adler 提交于
-
- 06 7月, 2015 1 次提交
-
-
由 Mark Adler 提交于
-
- 25 4月, 2014 1 次提交
-
-
由 Mark Adler 提交于
An open() with O_APPEND followed by an lseek() to determine the position will return zero for a non-empty file, even though the next write will start at the end of the file. This commit works around that by doing an lseek() to the end when appending.
-
- 25 3月, 2013 2 次提交
-
-
由 Mark Adler 提交于
-
由 Mark Adler 提交于
You would still need to run zlib2ansi on all of the *.c files.
-
- 13 8月, 2012 1 次提交
-
-
由 Mark Adler 提交于
This patch allows zlib to compile cleanly with the -Wcast-qual gcc warning enabled, but only if ZLIB_CONST is defined, which adds const to next_in and msg in z_stream and in the in_func prototype. A --const option is added to ./configure which adds -DZLIB_CONST to the compile flags, and adds -Wcast-qual to the compile flags when ZLIBGCCWARN is set in the environment.
-
- 23 5月, 2012 1 次提交
-
-
由 Mark Adler 提交于
-
- 03 5月, 2012 1 次提交
-
-
由 Mark Adler 提交于
This avoids warnings in OpenBSD that apparently can't be turned off whenever you link strcpy, strcat, or sprintf. When snprintf isn't available, the use of the "unsafe" string functions has always in fact been safe, since the lengths are all checked before those functions are called. We do not use strlcpy or strlcat, since they are not (yet) found on all systems. snprintf on the other hand is part of the C standard library and is very common.
-
- 19 3月, 2012 3 次提交
-
-
由 Mark Adler 提交于
The conversion to multi-byte will be locale-specific, but it's better than nothing and is only to provide more information in the error message returned by gz_error(). The conversion has no effect on what's opened.
-
由 Mark Adler 提交于
-
由 Mark Adler 提交于
Also need to #include <stddef.h> for zlib.h, and need to workaround the inability to use wide characters in constructed error messages with zlib's interface.
-
- 18 3月, 2012 1 次提交
-
-
由 Mark Adler 提交于
-
- 17 3月, 2012 1 次提交
-
-
由 Mark Adler 提交于
-
- 11 3月, 2012 2 次提交
-
-
由 Mark Adler 提交于
-
由 Mark Adler 提交于
-
- 05 3月, 2012 1 次提交
-
-
由 Mark Adler 提交于
-
- 04 3月, 2012 1 次提交
-
-
由 Mark Adler 提交于
-
- 19 12月, 2011 1 次提交
-
-
由 Mark Adler 提交于
-
- 12 12月, 2011 1 次提交
-
-
由 Mark Adler 提交于
Before, gzeof() would return true (accurately) when the last read request went just up to the end of the uncompressed data. In the analogous case, feof() would return false, only returning true when a read request goes past the end of the file. This patch corrects gzeof() to behave in the same way as feof(), as noted in the zlib.h documentation.
-
- 03 10月, 2011 1 次提交
-
-
由 Mark Adler 提交于
-
- 02 10月, 2011 1 次提交
-
-
由 Tor Lillqvist 提交于
-
- 01 10月, 2011 1 次提交
-
-
由 Mark Adler 提交于
-
- 27 9月, 2011 3 次提交
-
-
由 Mark Adler 提交于
-
由 Mark Adler 提交于
-
由 Mark Adler 提交于
-
- 26 9月, 2011 1 次提交
-
-
由 Mark Adler 提交于
Before this fix, gzread() would lose data if a premature end of file was encountered. This prevented gzread() from being used on a file that was being written concurrently. Now gzread() returns all of the data it has available before indicating a premature end of file. This also changes the error returned on a premature end of file from Z_DATA_ERROR to Z_BUF_ERROR. This allows the user to determine if the error is recoverable, which it is if Z_BUF_ERROR is returned. If a Z_DATA_ERROR is returned, then the error is not recoverable. This patch replaces the functionality of a previous patch that fixed reading through an empty gzip stream in a concatenation of gzip streams. To implement this fix, a noticeable rewrite of gzread.c was needed. The patch has the added advantage of using inflate's gzip processing instead of replicating the functionality in gzread.c. This makes the gz code a little simpler.
-
- 12 9月, 2011 1 次提交
-
-
由 Mark Adler 提交于
-
- 10 9月, 2011 4 次提交
-
-
由 Mark Adler 提交于
-
由 Mark Adler 提交于
-
由 Mark Adler 提交于
-
由 Mark Adler 提交于
-