test 1560: avoid valgrind false positives
When using maximum code optimization level (-O3), valgrind wrongly detects uses of uninitialized values in strcmp(). Preset buffers with all zeroes to avoid that.
This commit is contained in:
parent
1369b8ad31
commit
a75f12768d
@ -60,7 +60,7 @@ static int checkparts(CURLU *u, const char *in, const char *wanted,
|
||||
{CURLUPART_FRAGMENT, "fragment"},
|
||||
{0, NULL}
|
||||
};
|
||||
buf[0] = 0;
|
||||
memset(buf, 0, sizeof(buf));
|
||||
|
||||
for(i = 0; parts[i].name; i++) {
|
||||
char *p = NULL;
|
||||
@ -645,6 +645,9 @@ static CURLUcode updateurl(CURLU *u, const char *cmd, unsigned int setflags)
|
||||
char buf[80];
|
||||
char part[80];
|
||||
char value[80];
|
||||
|
||||
memset(part, 0, sizeof(part)); /* Avoid valgrind false positive. */
|
||||
memset(value, 0, sizeof(value)); /* Avoid valgrind false positive. */
|
||||
memcpy(buf, p, n);
|
||||
buf[n] = 0;
|
||||
if(2 == sscanf(buf, "%79[^=]=%79[^,]", part, value)) {
|
||||
|
||||
Loading…
Reference in New Issue
Block a user