summaryrefslogtreecommitdiff
path: root/string-list.c
diff options
context:
space:
mode:
authorJeff King <peff@peff.net>2011-02-12 05:18:51 (GMT)
committerJunio C Hamano <gitster@pobox.com>2011-02-14 18:55:03 (GMT)
commit62b8102c60a716e66cfd2a33e596e9d5be134267 (patch)
treed3def01dc545c9ba7d4bf6962f0c8ca139928572 /string-list.c
parentdab0d4108d7b45905a12ec6cea2cfc20ea8eabef (diff)
downloadgit-62b8102c60a716e66cfd2a33e596e9d5be134267.zip
git-62b8102c60a716e66cfd2a33e596e9d5be134267.tar.gz
git-62b8102c60a716e66cfd2a33e596e9d5be134267.tar.bz2
string_list_append: always set util pointer to NULL
It is not immediately obvious that the util field may contain random bytes after appending an item. Especially since the string_list_insert* functions _do_ explicitly zero the util pointer. This does not appear to be a bug in any current git code, as all callers either fill in the util field immediately or never use it. However, it is worth it to be less surprising to new users of the string-list API who may expect it to be intialized to NULL. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'string-list.c')
-rw-r--r--string-list.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/string-list.c b/string-list.c
index 9b023a2..5168118 100644
--- a/string-list.c
+++ b/string-list.c
@@ -153,6 +153,7 @@ struct string_list_item *string_list_append(struct string_list *list, const char
ALLOC_GROW(list->items, list->nr + 1, list->alloc);
list->items[list->nr].string =
list->strdup_strings ? xstrdup(string) : (char *)string;
+ list->items[list->nr].util = NULL;
return list->items + list->nr++;
}