From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@zsh.org
Subject: Re: Probabilistic crash on zsh 5.9 on x86_64
Date: Thu, 13 Apr 2023 12:12:25 +0100 (BST) [thread overview]
Message-ID: <1621107110.4161180.1681384345108@mail.virginmedia.com> (raw)
In-Reply-To: <267594676.4158370.1681382869709@mail.virginmedia.com>
> On 13/04/2023 11:47 Peter Stephenson <p.w.stephenson@ntlworld.com> wrote:
> > On 11/04/2023 17:29 Peter Stephenson <p.w.stephenson@ntlworld.com> wrote:
> > This indicates something is wrong with the reference counting:
> > it shouldn't be possible for a shell code chunk to be visible
> > to the user without it being marked as having at least one reference.
>
> This should reliably pick up the problem, though it needs tracing back
> to where the function is set up.
"watch" says the real culprit is this unsettrap() in starttrapscope().
I guess the save and restore action here needs a corresponding
useeprog / freeprog, not sure the best way of doing that yet.
/*
* SIGEXIT needs to be restored at the current locallevel,
* so give it the next higher one. dosavetrap() is called
* automatically where necessary.
*/
if (sigtrapped[SIGEXIT] && !exit_trap_posix) {
locallevel++;
unsettrap(SIGEXIT);
locallevel--;
}
pws
next prev parent reply other threads:[~2023-04-13 11: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 [this message]
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
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
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=1621107110.4161180.1681384345108@mail.virginmedia.com \
--to=p.w.stephenson@ntlworld.com \
--cc=zsh-workers@zsh.org \
/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).