Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: Bug: Null byte in shell history causes segfault during $historywords reverse subscripting

X-seq: zsh-workers 51801
From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
To: Eric Freese <ericdfreese@xxxxxxxxx>
Cc: zsh-workers@xxxxxxx
Subject: Re: Bug: Null byte in shell history causes segfault during $historywords reverse subscripting
Date: Fri, 26 May 2023 18:46:35 -0700
Archived-at: <https://zsh.org/workers/51801>
In-reply-to: <CAAikoAL0hiooRDJu=JdPqfQH_kZV+O-+D1iETKrV5JF3oNRiCA@mail.gmail.com>
List-id: <zsh-workers.zsh.org>
References: <CAAikoAL0hiooRDJu=JdPqfQH_kZV+O-+D1iETKrV5JF3oNRiCA@mail.gmail.com>

On Fri, May 26, 2023 at 12:37 PM Eric Freese <ericdfreese@xxxxxxxxx> wrote:
>
> I've come across a segfault when shell history has been loaded from a
> file and contains a command where a null byte was entered into the
> line editor via ^V^@ (opposed to typing as $'\0'). Reverse
> subscripting $historywords on a pattern that does not match triggers
> the error.

I can't reproduce a crash with workers/51739 - does your build have that commit?

However, I do get:
BUG: substring ends in the middle of a metachar in ztrsub()

Follow-Ups:
- Re: Bug: Null byte in shell history causes segfault during $historywords reverse subscripting
  - From: Bart Schaefer

References:
- Bug: Null byte in shell history causes segfault during $historywords reverse subscripting
  - From: Eric Freese

Messages sorted by: Reverse Date, Date, Thread, Author