[Zlib-devel] Second zlib 1.2.4 candidate
Török Edwin
edwintorok at gmail.com
Sun Mar 14 12:59:08 EDT 2010
On 03/14/2010 06:46 PM, Gilles Vollant wrote:
> do you have more info (the valgrind dump with line number)?
> "
> Also the valgrind warning about use of uninitialized value is gone
> (which is present in 1.2.3.4), this was fixed already in an earlier beta
> I think."
>
This is the valgrind warning with zlib 1.2.3.4:
==30203== Conditional jump or move depends on uninitialised value(s)
==30203== at 0x56E69FF: inflateReset2 (inflate.c:157)
==30203== by 0x56E6B53: inflateInit2_ (inflate.c:193)
==30203== by 0x4CA3F9A: cli_scangzip (scanners.c:475)
==30203== by 0x4CA21B2: cli_magic_scandesc (scanners.c:2021)
==30203== by 0x4CA27D8: cl_scandesc (scanners.c:2334)
==30203== by 0x407080: scanfile (manager.c:138)
==30203== by 0x407F91: scanmanager (manager.c:608)
==30203== by 0x4068C9: main (clamscan.c:147)
It got fixed in 1.2.3.7 (1.2.3.6 has it, 1.2.3.7 no):
Changes in 1.2.3.7 (24 Jan 2010)
.....
- Avoid access of uninitialized data for first inflateReset2 call [Gomes]
Best regards,
--Edwin
More information about the Zlib-devel
mailing list