From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21105 invoked by alias); 14 Jan 2017 22:13:09 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 40363 Received: (qmail 28005 invoked from network); 14 Jan 2017 22:13:09 -0000 X-Qmail-Scanner-Diagnostics: from mercury.zanshin.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(64.84.47.142):SA:0(-0.0/5.0):. Processed in 0.753278 secs); 14 Jan 2017 22:13:09 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at ipost.com designates 64.84.47.142 as permitted sender) Date: Sat, 14 Jan 2017 14:12:35 -0800 (PST) From: Bart Schaefer Reply-To: Bart Schaefer To: zsh-workers@zsh.org Subject: Re: BUG: Zsh crashes In-Reply-To: <20170114221052.12a4539b@ntlworld.com> Message-ID: References: <20170113175242.16210658@pwslap01u.europe.root.pri> <20170114010859.GA22474@tower.spodhuis.org> <20170114024833.GA26958@fujitsu.shahaf.local2> <20170114203624.2c396d08@ntlworld.com> <20170114221052.12a4539b@ntlworld.com> User-Agent: Alpine 2.00 (LRH 1167 2008-08-23) X-Face: "f/X=UCVgd*^c>+x(gMq0at?e:woX+;'snkkRzc3SX<0AZ (/PS4.M2hzGS9X:Qj]at_H/%a9K}:-eS<"v_7vX84PG9Bf Zpb`wI!I4geY=or+nWq`3CX`oq&TJR;g^ps|7(MH?jh;bs %vHJfCh5>a*6Re5m|Bidja\\o]>n\A)ib1:yX*T`zR(*h~ %tOw<~!D9{e6h!8M2:d8G2@K>y^1I_Vdy\d\MYe]z7c MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sat, 14 Jan 2017, Peter Stephenson wrote: > On Sat, 14 Jan 2017 20:36:24 +0000 > Peter Stephenson 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? That's certainly the direction my investigation was going. It almost *has* to be *something* about bin_compvalues().