From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Unitialized memory reads again.
Date: Thu, 15 Jun 2000 11:29:22 +0200 (MET DST) [thread overview]
Message-ID: <200006150929.LAA06651@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Felix Rosencrantz's message of Wed, 14 Jun 2000 21:41:10 -0700 (PDT)
Felix Rosencrantz wrote:
> Sorry to report that I started seeing new uninitialized memory reads
> during completion. Now at different location.
> match_str [compmatch.c:806]
> match_str [compmatch.c:598]
> match_str [compmatch.c:598]
> addmatches [compcore.c:1801]
> bin_compadd [complete.c:606]
> ---------------------------------
> match_str [compmatch.c:806]
> match_str [compmatch.c:598]
> addmatches [compcore.c:1801]
> bin_compadd [complete.c:606]
>
> Though these seem to be more difficult to trip over.
Before using the patch below, could you try if `setopt __listbeep__<TAB>'
shows the bad behaviour (probably adding more `_'s to the end)? If it
does, the patch below should fix it (of course, with uninitialized
memory reads it could be that this is the problem but it doesn't show
up, sigh).
> The recent changes to the trap code have fixed the memory leaks
> reported in 11766, and no new errors.
Good. I was about to ask.
> Sven, thanks for the stat optimizations to _path_files. It seems faster.
> Plus, file completion works nicely with Clearcase now. (Though... the
> additional change you were suggesting in workers/9631 for a "style that
> gives a pattern to match pathname components that should be accepted
> immediately" would make it work even better... :) )
I had forgotten about that... we'll see.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-06-15 9:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-15 9:29 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-15 4:41 Felix Rosencrantz
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=200006150929.LAA06651@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--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).