[Bug 789] gunzip/bunzip2/zcat output corrupted

bugzilla at busybox.net bugzilla at busybox.net
Fri Dec 11 11:41:36 UTC 2009


https://bugs.busybox.net/show_bug.cgi?id=789





--- Comment #4 from Michael McTernan <mmcternan at airvana.com>  2009-12-11 11:41:36 UTC ---
(In reply to comment #3)
> 
> What is the CPU and architecture where it fails? Is it big endian?

ARM Cortex A8, so armv7-a.  It's little endian.

> If it is not reproducible on x86, we may end up in situation when only you can
> debug it.

I did wonder if this would be the case.  

> In case it is just a case where we end up using an uninitialized variable
> somewhere, one quick & dirty method to test this theory is to go to
> decompress_unzip.c and add "= 0" / to every uninitialized local variable and
> memset to 0 every local uninitialized array, like this:

Yeah - this is why I tried Valgrind on x86 - it's good at reporting errors on
use of uninitialised data.  

I'll try gcc with -Wuninitialized and -Winit-self first, then try poking around
the code as you say.  It might be a while before I come back...


-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the busybox-cvs mailing list