From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk,
Frank Terbeck <frank.terbeck@rwth-aachen.de>,
367823-forwarded@bugs.debian.org
Subject: Re: Bug#367823: zsh: segfault when completing arrays
Date: Fri, 19 May 2006 11:05:55 +0100 [thread overview]
Message-ID: <200605191005.k4JA5tjK025536@news01.csr.com> (raw)
In-Reply-To: <20060518131226.GA19838@scowler.net>
Clint Adams wrote:
> > Howdy.
> > zsh 4.3.2 crashes with sig11 when doing the following:
> >
> > [snip]
> > % zsh -f
> > % autoload compinit; compinit
> > % array=( 5 4 3 2 1 )
> > % print $array[4]
> > ^- place your cursor here and hit <TAB>
> > [snap]
> >
> > I've tested this on a sarge system with zsh 4.2.5 and that version is
> > not affected by this problem.
>
> Should zlemetaline be 0 or should zleline + zlemetacs be non-zero?
I suspect it's just a typo...
Index: Src/Zle/zle_params.c
===================================================================
RCS file: /cvsroot/zsh/zsh/Src/Zle/zle_params.c,v
retrieving revision 1.28
diff -u -r1.28 zle_params.c
--- Src/Zle/zle_params.c 7 Mar 2006 21:31:43 -0000 1.28
+++ Src/Zle/zle_params.c 19 May 2006 10:04:48 -0000
@@ -300,7 +300,8 @@
get_rbuffer(UNUSED(Param pm))
{
if (zlemetaline != NULL)
- return dupstrpfx((char *)zleline + zlemetacs, zlemetall - zlemetacs);
+ return dupstrpfx((char *)zlemetaline + zlemetacs,
+ zlemetall - zlemetacs);
return zlelineasstring(zleline + zlecs, zlell - zlecs, 0, NULL, NULL, 1);
}
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK Tel: +44 (0)1223 692070
To access the latest news from CSR copy this link into a web browser: http://www.csr.com/email_sig.php
prev parent reply other threads:[~2006-05-19 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060518120635.11242.54875.reportbug@fsst.voodoo.lan>
2006-05-18 13:12 ` Clint Adams
2006-05-19 10:05 ` Peter Stephenson [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=200605191005.k4JA5tjK025536@news01.csr.com \
--to=pws@csr.com \
--cc=367823-forwarded@bugs.debian.org \
--cc=frank.terbeck@rwth-aachen.de \
--cc=zsh-workers@sunsite.dk \
/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).