3 Commits

Author	SHA1	Message	Date
skal	757ebcb1c1	catch malloc(0)/calloc(0) with an assert ... Actually, it turns out we now should never call these functions with a zero size, otherwise something is wrong in the logic. Change-Id: Ie414fcbec95486c169190470a71f2cff0843782a	2013-01-23 20:09:28 +01:00
skal	42f8f9346c	handle malloc(0) and calloc(0) uniformly on all platforms ... also change lossless encoder logic, which was relying on explicit NULL return from WebPSafeMalloc(0) renamed function to CheckSizeArgumentsOverflow() explicitly addresses issue #138 Change-Id: Ibbd51cc0281e60e86dfd4c5496274399e4c0f7f3	2013-01-22 23:40:16 +01:00
Pascal Massimino	80cc7303ab	WebPCheckMalloc() and WebPCheckCalloc(): ... safe size-checking versions of malloc() and calloc() Change-Id: Iffa3138c48b9b254b3d7eaad913e1f852d9dafba	2012-07-31 16:56:39 -07:00