From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Memory access bug with negative subscripts
Date: Tue, 24 Jul 2007 21:52:22 -0700 [thread overview]
Message-ID: <070724215222.ZM4902@torch.brasslantern.com> (raw)
This bug appears at least as far back as zsh 3.0.5, and probably longer
ago. Still happens in the latest CVS co from SourceForge.
x=x
x[-10]=y
print $x
I can't predict what you'll see, but unless you get very lucky it won't
be what you ought to see. For example,
torch% x[-$RANDOM]=z
torch% print $x
zpasswd
I imagine running that under ElectricFence or some similar memory checker
would be instructive.
next reply other threads:[~2007-07-25 4:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 4:52 Bart Schaefer [this message]
2007-07-25 9:22 ` Peter Stephenson
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=070724215222.ZM4902@torch.brasslantern.com \
--to=schaefer@brasslantern.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).