From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: Zsh workers <zsh-workers@sunsite.dk>
Subject: Re: completion matching problem with 4.3.8
Date: Thu, 30 Oct 2008 16:43:40 +0100 [thread overview]
Message-ID: <19187.1225381420@thecus> (raw)
In-Reply-To: <18981.1225379134@thecus>
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
next prev parent reply other threads:[~2008-10-30 15:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 11:28 Oliver Kiddle
2008-10-30 12:17 ` Peter Stephenson
2008-10-30 13:13 ` Oliver Kiddle
2008-10-30 14:11 ` Peter Stephenson
2008-10-30 15:05 ` Oliver Kiddle
2008-10-30 15:43 ` Oliver Kiddle [this message]
2008-10-30 20:21 ` Peter Stephenson
2008-10-30 22:00 ` Peter Stephenson
2008-10-31 9:08 ` Oliver Kiddle
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=19187.1225381420@thecus \
--to=okiddle@yahoo.co.uk \
--cc=zsh-workers@sunsite.dk \
/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).