From: Bart Schaefer <schaefer@brasslantern.com>
To: martin.ebourne@arcordia.com, zsh-workers@sunsite.dk
Subject: Re: Very odd behaviour with zsh, maybe corruption bug
Date: Thu, 11 Oct 2001 16:30:54 +0000 [thread overview]
Message-ID: <1011011163054.ZM18442@candle.brasslantern.com> (raw)
In-Reply-To: <OFFE2ABA9E.2332FF4A-ON80256AE2.0038ACE5@uk.jpmorgan.com>
On Oct 11, 11:57am, martin.ebourne@arcordia.com wrote:
}
} SunOS gdd-odybin2 5.6 Generic_105181-28 sun4u sparc
} SUNW,Ultra-Enterprise-10000
}
} gdd-odybin2% +_down_fn:3> [[ new-up == new-up ]]
} +_down_fn:8> [[ "abc
} def" == *
} * ]]
} +_down_fn:10> _searching=
} +_down_fn:11> zle .down-line-or-history
I can't reproduce this on my linux machine, even after ten minutes or so
of fooling with it.
For [[ ]], the trace output is generated before the right-hand-side is
copied and compiled into a pattern for comparison to the left-hand-side,
so it could be the case that memory errors result in a bad comparison;
but they'd be far more likely to produce a "bad pattern" error instead.
This is a long, long, long shot, but: You don't happen to be using a
debug trap? (I.e., a TRAPDEBUG function, or `trap ... DEBUG')
Have you tried configuring with --enable-zsh-debug ?
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-10-11 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 10:57 martin.ebourne
2001-10-11 16:30 ` Bart Schaefer [this message]
2001-10-12 5:02 ` Bart Schaefer
2001-10-14 21:56 ` PATCH: " Bart Schaefer
2001-10-15 11:24 ` Sven Wischnowsky
2001-10-11 17:09 martin.ebourne
2001-10-12 9:19 martin.ebourne
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=1011011163054.ZM18442@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=martin.ebourne@arcordia.com \
--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).