From: Peter Stephenson <firstname.lastname@example.org>
Subject: Re: Probabilistic crash on zsh 5.9 on x86_64
Date: Thu, 13 Apr 2023 15:13:30 +0100 (BST) [thread overview]
Message-ID: <email@example.com> (raw)
> On 13/04/2023 15:03 Peter Stephenson <firstname.lastname@example.org> wrote:
> > On 13/04/2023 14:19 Peter Stephenson <email@example.com> wrote:
> > ...not trivial...
> > ...hard to know...
> > ...Unfortunately...
> > ...more complicated than that...
> > ...isn't trivial...
> Have a look at this --- it simply marks the prog in the shell function as
> in use earlier and unmarks it later, so the shenanigans within to do
> with traps all come out in the wash. So, in theory, there's not much
> to go wrong. But let me know...
One note (the only caveat that springs to mind, but probably worth mentioning)
is that if a function is freed explicitly or implicitly inside the hierarchy
that handles it, we don't actually gain the memory back until a bit later
than previously. I think this would happen with the placeholder structure
for an autoloadable shell function, for example. Hopefully that's not a
big deal, but unless I mention it someone's sure to come up with a case
where it is...
next prev parent reply other threads:[~2023-04-13 14:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-08 17:28 zsh bug report throwaway email thing
2023-04-08 21:36 ` Mikael Magnusson
2023-04-11 16:14 ` Jun. T
2023-04-11 16:29 ` Peter Stephenson
2023-04-13 10:47 ` Peter Stephenson
2023-04-13 11:12 ` Peter Stephenson
2023-04-13 13:02 ` Jun. T
2023-04-13 13:19 ` Peter Stephenson
2023-04-13 14:03 ` Peter Stephenson
2023-04-13 14:13 ` Peter Stephenson [this message]
2023-04-13 16:40 ` Jun. T
2023-04-13 16:55 ` Peter Stephenson
2023-04-14 8:29 ` Peter Stephenson
2023-04-14 12:21 ` Mikael Magnusson
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).