From: pacman@cqc.com
To: zsh-workers@math.gatech.edu
Subject: Re: recipe for a ZLE segfault
Date: Tue, 18 Aug 1998 13:35:25 -0500 (EST) [thread overview]
Message-ID: <19980818183525.15460.qmail@defiant.cqc.com> (raw)
In-Reply-To: <199808181029.MAA07660@hydra.ifh.de> from "Peter Stephenson" at Aug 18, 98 12:29:57 pm
Peter Stephenson writes the following:
>
>I get this too. Does this fix it? (It looks like it's necessary anyway,
>according to my reading of mkundoent().)
>
>*** Src/Zle/zle_utils.c.ch Wed Apr 29 23:42:46 1998
>--- Src/Zle/zle_utils.c Tue Aug 18 12:24:07 1998
>***************
>*** 516,521 ****
>--- 516,522 ----
> line[ll - 1 - suf] == lastline[lastll - 1 - suf]; )
> suf++;
> ch = zalloc(sizeof(*ch));
>+ ch->next = NULL;
> ch->hist = histline;
> ch->off = pre;
> if(suf + pre == lastll)
Yes, this takes care of it.
--
Alan Curry
prev parent reply other threads:[~1998-08-18 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-18 5:22 pacman
1998-08-18 10:29 ` Peter Stephenson
1998-08-18 18:35 ` pacman [this message]
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=19980818183525.15460.qmail@defiant.cqc.com \
--to=pacman@cqc.com \
--cc=zsh-workers@math.gatech.edu \
/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).