zsh-workers
 help / color / mirror / code / Atom feed
From: "Johan Ström" <johan@stromnet.se>
To: Jun T <takimoto-j@kba.biglobe.ne.jp>, zsh-workers@zsh.org
Subject: Re: 5.9 core dumps under zleentry->zleread->zlecore
Date: Fri, 3 Jun 2022 09:19:56 +0200	[thread overview]
Message-ID: <0de54d92-cda4-8297-d688-b9dd6ac7ab12@stromnet.se> (raw)
In-Reply-To: <EE5C14E3-B3AF-4732-88EF-FBA78B27F781@kba.biglobe.ne.jp>

On 2022-06-03 09:14, Jun T wrote:
>> 2022/06/02 16:11, Johan Ström <johan@stromnet.se> wrote:
>>
>> Now upgraded to 5.9, and similar behavior, after some idle periods of some days, returned to terminal and at first use, it crashed.
> It seems that you get core dumps after "upgrede".
> How did you upgrade your zsh?  By 'pacman -Syu' ?
> If so, have you rebooted your OS after the upgrade?

Yes, full system update including reboot:

[2021-07-30T11:37:51+0200] [ALPM] installed zsh (5.8-1)
[2022-02-16T08:14:00+0100] [ALPM] upgraded zsh (5.8-1 -> 5.8.1-1)
[2022-05-11T18:36:51+0200] [ALPM] upgraded zsh (5.8.1-1 -> 5.8.1-2)
[2022-05-26T11:01:13+0200] [ALPM] upgraded zsh (5.8.1-2 -> 5.9-1)
[2022-06-02T11:23:37+0200] [ALPM] reinstalled zsh (5.9-1)   # this was 
my install of the debug-enabled package

Before 5.8.1 (16'th feb) I never had any issues with zsh.
Haven't made any changes to .zshrc (posted in previous thread) at all 
before or after (but I cannot say for sure if some other package's zsh 
additions (/usr/share/zsh/site-functions?) might have been altered).



  reply	other threads:[~2022-06-03  7:20 UTC|newest]

Thread overview: 10+ 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 [this message]
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

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=0de54d92-cda4-8297-d688-b9dd6ac7ab12@stromnet.se \
    --to=johan@stromnet.se \
    --cc=takimoto-j@kba.biglobe.ne.jp \
    --cc=zsh-workers@zsh.org \
    --subject='Re: 5.9 core dumps under zleentry->zleread->zlecore' \
    /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).