Fix unintialized value bug in gzputc() introduced by const patches.
authorMark Adler <madler@alumni.caltech.edu>
Fri, 24 Aug 2012 22:02:28 +0000 (15:02 -0700)
committerMark Adler <madler@alumni.caltech.edu>
Fri, 24 Aug 2012 22:02:28 +0000 (15:02 -0700)
commitaa566e86c46d2264bf623e51f5840bde642548ad
treeccb156a5103cc7e6ced71e88f444acdb0e12654e
parent17068938ce5544ec3728402abd39bf3c55aec113
Fix unintialized value bug in gzputc() introduced by const patches.

Avoid the use of an uninitialized value when the write buffers have
not been initialized.  A recent change to avoid the use of strm->
next_in in order to resolve some const conflicts added the use of
state->in in its place.  This patch avoids the use of state->in
when it is not initialized.  Nothing bad would actually happen,
since two variables set to the same unintialized value are
subtracted.  However valgrind was rightly complaining.  So this
fixes that.
gzwrite.c