From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Segfault with "private" parameters inside "always" block
Date: Thu, 9 Jun 2022 14:03:22 -0700 [thread overview]
Message-ID: <CAH+w=7a4Wr3wXN5VtC=Ctmvtw=4K-6spFW8mXqC8ZaoHh87t8g@mail.gmail.com> (raw)
zsh/param/private assumes the heap created in startparamscope() is the
only active heap until endparamscope(), but "always" blocks allocate
and free another layer of heap, which invalidates the memory "private"
uses for the parameter GSU structures.
I haven't figured out what to do about this, yet. The GSUs can't just
be static, because different special params use different callbacks
for get/set/unset.
next reply other threads:[~2022-06-09 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 21:03 Bart Schaefer [this message]
2022-06-09 22:04 ` [PATCH] " 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='CAH+w=7a4Wr3wXN5VtC=Ctmvtw=4K-6spFW8mXqC8ZaoHh87t8g@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
--subject='Re: Segfault with "private" parameters inside "always" block' \
/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
Code repositories for project(s) associated with this 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).