Re: completion matching problem with 4.3.8

[Oliver Kiddle <okiddle@xxxxxxxxxxx>]

I wrote:
> My gcc build is failing on configure but I'll let you know.

Turns out it was finding libgdbm in /opt/csw but needed the rpath
setting up.

Anyway, the gcc built zsh also has the problem so it isn't compiler
related. I tried running the minimal zsh -f, compctl test on Linux
through valgrind and I get the following message. Maybe valgrind has
found the source of the problem:

==647== Conditional jump or move depends on uninitialised value(s)
==647==    at 0x66E0ADD: pattern_match_restrict (compmatch.c:1276)
==647==    by 0x66E1781: bld_line (compmatch.c:1811)
==647==    by 0x66E26D4: join_sub (compmatch.c:2123)
==647==    by 0x66E2E96: join_psfx (compmatch.c:2362)
==647==    by 0x66E42C4: join_clines (compmatch.c:2805)
==647==    by 0x66DAF04: add_match_data (compcore.c:2879)
==647==    by 0x68FA4BE: addmatch (compctl.c:2020)
==647==    by 0x6900018: makecomplistflags (compctl.c:3629)
==647==    by 0x68FBBCF: makecomplistlist (compctl.c:2595)
==647==    by 0x68FBAA6: makecomplistor (compctl.c:2559)
==647==    by 0x68FBA30: makecomplistcc (compctl.c:2536)
==647==    by 0x68FB864: makecomplistcmd (compctl.c:2492)

Valgrind also finds some leaked memory from parse_class (complete.c:467)
with the same test.

Oliver