From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org, Ray Andrews <rayandrews@eastlink.ca>
Subject: Re: zsh-5.2-test-3
Date: Sat, 10 Dec 2016 19:07:37 -0800 [thread overview]
Message-ID: <161210190737.ZM11109@torch.brasslantern.com> (raw)
In-Reply-To: <584CB4EF.6070904@eastlink.ca>
[Moving to -workers]
On Dec 10, 6:07pm, Ray Andrews wrote:
} Subject: Re: zsh-5.2-test-3
}
} On 12/09/2016 11:54 AM, Peter Stephenson wrote:
} >
} > 5.2-test-3 is in
} >
} > http://www.zsh.org/pub/development/
} >
} >
} Seems to have fired up ok, however:
What is the platform where you are compiling?
}
} builtin.c:5041:11: warning: "cursplit" may be used uninitialized in
} this function [-Wmaybe-uninitialized]
}
} compmatch.c:774:15: warning: "savl" may be used uninitialized in
} this function [-Wmaybe-uninitialized]
These are both spurious -- each of these variables shadows another which
is always used/tested first and which is not used uninitialized. May as
well shut up the warnings, though.
} $ make check
}
} ./V10private.ztst: starting.
} Pattern match failed:
}
}
There ought to be more output than that ... please run
$ ZTST_verbose=2 make check TESTNUM=V10
} BTW, if there a 'make check' that only shows errors or warnings? No
} need to see all the stuff that's fine.
No, but as shown above you can run specific tests if you already know
the others to be OK.
diff --git a/Src/Zle/compmatch.c b/Src/Zle/compmatch.c
index f82f00e..aedf463 100644
--- a/Src/Zle/compmatch.c
+++ b/Src/Zle/compmatch.c
@@ -674,7 +674,7 @@ match_str(char *l, char *w, Brinfo *bpp, int bc, int *rwlp,
*
* operation. Similar to savw.
*/
- char savl;
+ char savl = 0;
/*
* The anchor on this end.
*/
diff --git a/Src/builtin.c b/Src/builtin.c
index e641a97..65e0cb1 100644
--- a/Src/builtin.c
+++ b/Src/builtin.c
@@ -4092,7 +4092,7 @@ bin_print(char *name, char **args, Options ops, int func)
char *start, *endptr, *c, *d, *flag, *buf = NULL, spec[14], *fmt = NULL;
char **first, **argp, *curarg, *flagch = "'0+- #", save = '\0', nullstr = '\0';
size_t rcount = 0, count = 0;
- size_t *cursplit, *splits = 0;
+ size_t *cursplit = 0, *splits = 0;
FILE *fout = stdout;
#ifdef HAVE_OPEN_MEMSTREAM
size_t mcount;
next prev parent reply other threads:[~2016-12-11 3:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161206195028epcas2p3c53119ab37952571be3238cdf228d88f@epcas2p3.samsung.com>
[not found] ` <20161206194916.10448440@ntlworld.com>
2016-12-06 23:33 ` test failures on Solaris (was Re: zsh-5.2-test-2) Danek Duvall
2016-12-07 0:36 ` Bart Schaefer
[not found] ` <20161209095729.2033b5be@pwslap01u.europe.root.pri>
[not found] ` <20161209195457.27e43234@ntlworld.com>
[not found] ` <584CB4EF.6070904@eastlink.ca>
2016-12-11 3:07 ` Bart Schaefer [this message]
2016-12-11 3:26 ` zsh-5.2-test-3 Daniel Shahaf
2016-12-11 3:33 ` zsh-5.2-test-3 Bart Schaefer
2016-12-11 3:26 ` zsh-5.2-test-3 Ray Andrews
2016-12-11 3:44 ` zsh-5.2-test-3 Bart Schaefer
2016-12-11 3:59 ` zsh-5.2-test-3 Ray Andrews
2016-12-11 9:36 ` zsh-5.2-test-3 Bart Schaefer
2016-12-11 17:01 ` zsh-5.2-test-3 Ray Andrews
2016-12-11 17:14 ` zsh-5.2-test-3 Bart Schaefer
2016-12-11 4:11 ` zsh-5.2-test-3 Daniel Shahaf
2016-12-11 8:58 ` zsh-5.2-test-3 Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=161210190737.ZM11109@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=rayandrews@eastlink.ca \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).