zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@zsh.org
Subject: Re: BUG: Zsh crashes
Date: Sat, 14 Jan 2017 22:10:52 +0000	[thread overview]
Message-ID: <20170114221052.12a4539b@ntlworld.com> (raw)
In-Reply-To: <20170114203624.2c396d08@ntlworld.com>

On Sat, 14 Jan 2017 20:36:24 +0000
Peter Stephenson <p.w.stephenson@ntlworld.com> wrote:
> Removing the "=" after flowgraph stops it ("it" includes any reports of
> errors in mem.c, of course).  So this points at something to do with how
> _values handles values.

Can someone else see if this helps?

I have a feeling _rust ought to be quoting the "=", too, but that's much
more minor.

pws

diff --git a/Src/Zle/computil.c b/Src/Zle/computil.c
index 7bf9535..5b9ceec 100644
--- a/Src/Zle/computil.c
+++ b/Src/Zle/computil.c
@@ -3569,8 +3569,8 @@ bin_compvalues(char *nam, char **args, UNUSED(Options ops), UNUSED(int func))
 	    Cvval val = cv_get_val(cv_laststate.d, args[1]);
 
 	    if (val && val->arg) {
-		setsparam(args[2], val->arg->descr);
-		setsparam(args[3], val->arg->action);
+		setsparam(args[2], ztrdup(val->arg->descr));
+		setsparam(args[3], ztrdup(val->arg->action));
 
 		if (args[4])
 		    setsparam(args[4], ztrdup(val->name));


  reply	other threads:[~2017-01-14 22:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170113174208epcas1p109452434d2f95e52b24e49029ce15943@epcas1p1.samsung.com>
2017-01-13 17:40 ` Bjorn Baron
2017-01-13 17:52   ` Peter Stephenson
2017-01-14  1:09     ` Phil Pennock
2017-01-14  2:48       ` Daniel Shahaf
2017-01-14 20:19         ` Peter Stephenson
2017-01-14 20:36         ` Peter Stephenson
2017-01-14 22:10           ` Peter Stephenson [this message]
2017-01-14 22:12             ` Bart Schaefer
2017-01-15  2:32             ` Daniel Shahaf
2017-01-14  4:08     ` Eric Cook
2017-01-14  4:18       ` Eric Cook

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=20170114221052.12a4539b@ntlworld.com \
    --to=p.w.stephenson@ntlworld.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).