Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: [BUG] sigsegv
- X-seq: zsh-workers 51676
- From: Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>
- To: Zsh hackers list <zsh-workers@xxxxxxx>
- Subject: Re: [BUG] sigsegv
- Date: Fri, 28 Apr 2023 12:41:05 +0100 (BST)
- Archived-at: <https://zsh.org/workers/51676>
- Importance: Normal
- In-reply-to: <CAKc7PVC1Lm=iYHXM5MHSfOiGdHKdgD6nV1fnjn+-pok24Z5L_A@mail.gmail.com>
- List-id: <zsh-workers.zsh.org>
- References: <CAKc7PVDw98bvTSNWo4q52ZJ=i8vhRooKZHb-mOzenJVMoe1MFg@mail.gmail.com> <886115150.3264962.1682430985767@mail.virginmedia.com> <CAKc7PVC1Lm=iYHXM5MHSfOiGdHKdgD6nV1fnjn+-pok24Z5L_A@mail.gmail.com>
> On 28/04/2023 12:25 Sebastian Gniazdowski <sgniazdowski@xxxxxxxxx> wrote:
> It looks like the last field is incorrect:
>
> (gdb) up
> #1 0x00007ffff7e1f628 in histwgetfn (pm=0x508e10)
> at parameter.c:1241
> 1241 addlinknode(l, dupstring(h));
> (gdb) p *l->list->last
> Cannot access memory at address 0x7ffff5350068
You'll probably find this is tied to something in your history which
bufferwords() is processing incorrectly, as that's something of a
hack into the lexical analyser. If you can find what that is we
ought to be able to fix it at source.
However, making this code (taking out history words from a string
given the start and end) more robust seems like a good plan anyway.
pws
Messages sorted by:
Reverse Date,
Date,
Thread,
Author