zsh-workers
 help / color / mirror / code / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: zsh-workers@zsh.org
Subject: Re: Probabilistic crash on zsh 5.9 on x86_64
Date: Fri, 14 Apr 2023 14:21:07 +0200	[thread overview]
Message-ID: <CAHYJk3Sw=pVWkXoO7R7eb2fQFDOWdB9srgt2aBANNYxFBVchXQ@mail.gmail.com> (raw)
In-Reply-To: <300454748.2058336.1681460958361@mail.virginmedia.com>

On 4/14/23, Peter Stephenson <p.w.stephenson@ntlworld.com> wrote:
> Instead, here's a simple local fix-up which seems to keep valgrind quiet.
> It's not the most elegant thing I can imagine.
>
> diff --git a/Src/exec.c b/Src/exec.c
> index 3b3d1235e..274800b10 100644
> --- a/Src/exec.c
> +++ b/Src/exec.c
> @@ -5779,12 +5779,25 @@ doshfunc(Shfunc shfunc, LinkList doshargs, int
...
>      queue_signals();	/* Lots of memory and global state changes coming */
> +    /*
> +     * In case this is a special function such as a trap, mark it
> +     * is in use right now, so it doesn't get freed early.  The

"mark it as in use"

-- 
Mikael Magnusson


      reply	other threads:[~2023-04-14 12:21 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
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 [this message]

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='CAHYJk3Sw=pVWkXoO7R7eb2fQFDOWdB9srgt2aBANNYxFBVchXQ@mail.gmail.com' \
    --to=mikachu@gmail.com \
    --cc=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).