From: Gregory P. Smith <greg@krypto.org>
Date: Sat, 23 Nov 2013 20:21:28 +0000 (+0000)
Subject: gcc doesn't realize that dummy is always initialized by the function call
X-Git-Tag: v3.4.0b1~47
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=2b38fc187c2a764b7608cd262de5a2777a77f4c8;p=python

gcc doesn't realize that dummy is always initialized by the function call
and warns about potential uninitialized use.
Silence that by initializing it to null.
---

diff --git a/Modules/_pickle.c b/Modules/_pickle.c
index 4e0d86c69c..11e07b3902 100644
--- a/Modules/_pickle.c
+++ b/Modules/_pickle.c
@@ -1132,7 +1132,7 @@ _Unpickler_Read(UnpicklerObject *self, char **s, Py_ssize_t n)
         (self->frame_end_idx == -1 ||
          self->frame_end_idx <= self->next_read_idx)) {
         /* Need to read new frame */
-        char *dummy;
+        char *dummy = NULL;
         unsigned char *frame_start;
         size_t frame_len;
         if (_Unpickler_ReadUnframed(self, &dummy, FRAME_HEADER_SIZE) < 0)