From: Geoff Wing <mason@primenet.com.au>
To: zsh-workers@sunsite.dk
Subject: Re: Crash of 4.2.0-dev-1
Date: Sun, 11 Apr 2004 08:09:07 +0000 (UTC) [thread overview]
Message-ID: <slrnc7hv93.g5j.mason@g.primenet.com.au> (raw)
In-Reply-To: <1040411053038.ZM11840@candle.brasslantern.com>
Bart Schaefer <schaefer@brasslantern.com> typed:
: I presume of 4.2.0 also. Reproduce as follows:
:
: (1) Create a file "kshtest" in a directory in fpath. This file should NOT
: define the function "kshtest", that is, it's not a valid ksh-autoloadable
: file (but we're going to autoload it ksh-style anyway).
Any specific kshtest example for us?
% echo 'echo foo' > /usr/local/share/zsh/site-functions/kshtest
% zsh -f
% setopt kshautoload
% autoload +X -k kshtest
% kshtest
foo
foo
% kshtest
foo
% which kshtest
kshtest () {
echo foo
}
% echo $ZSH_VERSION
4.2.0
%
: (3) Observe the [correct] error:
:
: zsh: kshtest: function not defined by file
I don't understand why this is the correct error since you setopt kshautload.
Also, I haven't yet understood why it was run twice in my case (but I've been
sick so maybe my brain isn't working properly yet).
: (4) Memory is now corrupted. At some point soon, usually but not always
: during printing of the next prompt, the shell will crash in malloc().
I'm still going. Haven't seen any memory problems yet. Note that I use
the --enable-zsh-mem* args to configure.
Regards,
--
Geoff Wing
next prev parent reply other threads:[~2004-04-11 8:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-11 5:30 Bart Schaefer
2004-04-11 8:09 ` Geoff Wing [this message]
2004-04-11 16:09 ` Bart Schaefer
2004-04-11 22:40 ` Geoff Wing
2004-04-12 1:04 ` Bart Schaefer
2004-04-12 1:34 ` Felix Rosencrantz
2004-04-15 18:13 ` Peter Stephenson
2004-04-16 4:06 ` Bart Schaefer
2004-04-21 15:11 ` PATCH: " Peter Stephenson
2004-04-24 17:10 ` 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=slrnc7hv93.g5j.mason@g.primenet.com.au \
--to=mason@primenet.com.au \
--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).