From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Clint Adams <schizo@debian.org>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: 3.1.6-pws-6: $compstate[unambiguous] could be garbage
Date: Thu, 7 Oct 1999 21:36:58 +0000 [thread overview]
Message-ID: <991007213658.ZM27471@candle.brasslantern.com> (raw)
In-Reply-To: <19991007133016.A4805@dman.com>
On Oct 7, 1:30pm, Clint Adams wrote:
> Subject: Re: PATCH: 3.1.6-pws-6: $compstate[unambiguous] could be garbage
> > - } else {
> > + } else if (mnum != unambig_mnum || !ainfo || !scache) {
>
> Still getting things like
>
> _main_complete: bad pattern: x['^H8T^V@ [92]
Well, that certainly does appear that it could be caused by this or a
similar problem. `unambiguous' and `unambiguous_cursor' are the only keys
that have readonly computed values, and as it turns out they're both
computed by the same caching function, which is what caused the bug I saw
in the first place.
So if you get a debugger going and put a breakpoint in unambig_data() and
manage to see it free and reallocate the `scache' pointer twice, let us
know what `mnum', `unambig_mnum', and `ainfo' were when it happened.
One thing I tried while figuring out what was going on for the patch above
was inserting
noglob print -l x"${(@kv)^compstate}"x
immediately before line 92. That would at least tell you which assoc key
has the bad value.
next prev parent reply other threads:[~1999-10-07 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-07 10:40 Bart Schaefer
1999-10-07 17:30 ` Clint Adams
1999-10-07 21:36 ` Bart Schaefer [this message]
1999-10-08 7:46 ` Clint Adams
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=991007213658.ZM27471@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=schizo@debian.org \
--cc=zsh-workers@sunsite.auc.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).