zsh-workers
 help / color / mirror / code / Atom feed
From: "Johan Ström" <johan@stromnet.se>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: 5.9 core dumps under zleentry->zleread->zlecore
Date: Mon, 4 Dec 2023 11:49:43 +0100	[thread overview]
Message-ID: <b2b9def9-e935-4ebb-8850-3ea208e875f4@stromnet.se> (raw)
In-Reply-To: <CAH+w=7ZN9nBCPX+boPRrMZyreyGV5wjUfap5q66_Skya3-ecdA@mail.gmail.com>

On 2023-12-02 23:58, Bart Schaefer wrote:
> On Fri, Dec 1, 2023 at 12:00 AM Johan Ström <johan@stromnet.se> wrote:
>> Just had three terminals crash on me at once (after interacting with
>> them each).
> Given that the stack traces are all different, this suggests that
> something happening earlier is corrupting memory, which then causes an
> unrelated error.
>
> 1.  If possible, try building the latest dev revision.  There was
> recently a patch to resolve a number of issues flagged by Coverity
> code flow analysis.  There's also been a bad free fixed in process
> substitution (edge case not easily reached) and a fix for a reference
> counting error when using "zle -F" to watch file descriptors.
After some modifications to the arch AUR package zsh-git I know have the 
current master running. Let's see if problems go away.
Is master generally stable atm?
>
> 2.  Is there anything you're having zsh do while terminal input is
> idle?  ALRM handler (e.g., to update title bar), "zle -F" (see above),
> a "periodic" function, use of the zsh/sched module, etc.?

Nope, not that I'm aware of. This morning I opened the laptop which had 
been asleep since Friday, and on of the terminals immediately crashed 
when I interacted with history.
On my desktop I've had crashes too, but that machine never sleeps so not 
directly related to sleep at least.


Will report back if zsh-git works better, thanks for your prompt response!




  reply	other threads:[~2023-12-04 10:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02  7:11 Johan Ström
2022-06-02  7:31 ` Bart Schaefer
2022-06-02  9:25   ` Johan Ström
2022-06-03  7:14 ` Jun T
2022-06-03  7:19   ` Johan Ström
2022-06-03  9:53     ` Jun T
2022-06-03 10:02       ` Johan Ström
2022-06-04  3:32         ` Bart Schaefer
2022-06-04  7:39           ` Johan Ström
2022-06-04 20:06             ` Bart Schaefer
2023-12-01  8:00               ` Johan Ström
2023-12-02 22:58                 ` Bart Schaefer
2023-12-04 10:49                   ` Johan Ström [this message]
2023-12-05  1:47                     ` Bart Schaefer
2023-12-05  7:04                       ` Johan Ström

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=b2b9def9-e935-4ebb-8850-3ea208e875f4@stromnet.se \
    --to=johan@stromnet.se \
    --cc=schaefer@brasslantern.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).