help / color / mirror / code / Atom feed
From: zsh bug report throwaway email thing <zsh.throwaway.eDjb3nwqw@proton.me>
To: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Probabilistic crash on zsh 5.9 on x86_64
Date: Sat, 08 Apr 2023 17:28:43 +0000	[thread overview]
Message-ID: <tBWb5KtvEqjlaLFHtCcVrAmwPrj7aqaF50nYi_P69Xa6TiBh0ybu3JumnENwN5dGJJHi-unfO4E8igE27tXgSefdlNpUmOoAZ5fyBKSv2SU=@proton.me> (raw)

[-- Attachment #1: Type: text/plain, Size: 807 bytes --]


I would like to report a bug in zsh 5.9 (x86_64-pc-linux-gnu) (on Arch Linux, but I also reproduced on Alpine in QEMU, so it is probably zsh and not libc. Also, this does not happen in archiso in qemu, which is also weird.).

Repro instructions: run the commands:
TRAPEXIT() { ls }
# if that does not crash, keep typing TRAPEXIT until it does. sometimes it doesn't crash.

Expected behavior: zsh might throw an error or something? but it shouldn't crash
Actual behavior: there is an unknown chance that zsh throws an error and crashes like this:
zsh: TRAPEXIT: function not defined by file
malloc(): unaligned tcache chunk detected
[1] 34511 IOT instruction (core dumped) zsh

Nothing relevant in dmesg.

If I can help in any way, please contact me.

Kind regards,
an anonymous bug reporter

[-- Attachment #2: Type: text/html, Size: 2646 bytes --]

             reply	other threads:[~2023-04-08 17:29 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 [this message]
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

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='tBWb5KtvEqjlaLFHtCcVrAmwPrj7aqaF50nYi_P69Xa6TiBh0ybu3JumnENwN5dGJJHi-unfO4E8igE27tXgSefdlNpUmOoAZ5fyBKSv2SU=@proton.me' \
    --to=zsh.throwaway.edjb3nwqw@proton.me \
    --cc=zsh-workers@zsh.org \


* 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).