From: Bart Schaefer <schaefer@brasslantern.com>
To: Eric Freese <ericdfreese@gmail.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Bug: Null byte in shell history causes segfault during $historywords reverse subscripting
Date: Sat, 27 May 2023 00:33:08 -0700 [thread overview]
Message-ID: <CAH+w=7bF0WkU0WeSGx6PSYUM_eh0NQV+37=Ez+fEj=LL8g99VQ@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7aCePn+UwRHJ6mhcUCR5hRVZp7+ap-MNFooAMP-HTDiHg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 206 bytes --]
On Fri, May 26, 2023 at 6:46 PM Bart Schaefer <schaefer@brasslantern.com>
wrote:
>
> I can't reproduce a crash with workers/51739
Ah, it's not that commit, it's having compiled with DEBUG defined.
[-- Attachment #2: Type: text/html, Size: 351 bytes --]
next prev parent reply other threads:[~2023-05-27 7:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 19:37 Eric Freese
2023-05-27 1:46 ` Bart Schaefer
2023-05-27 7:33 ` Bart Schaefer [this message]
2023-06-05 7:11 ` Jun T
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='CAH+w=7bF0WkU0WeSGx6PSYUM_eh0NQV+37=Ez+fEj=LL8g99VQ@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=ericdfreese@gmail.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).