zsh-workers
 help / color / mirror / code / Atom feed
From: Marius van Wyk <marius@e.co.za>
To: Oliver Kiddle <okiddle@yahoo.co.uk>
Cc: zsh-workers@sunsite.dk
Subject: Re: ZSH 4.1.1 Coredump bug
Date: Mon, 16 Feb 2004 12:21:02 +0200	[thread overview]
Message-ID: <D2609C96-6069-11D8-AF48-000A958FBAFE@e.co.za> (raw)
In-Reply-To: <22466.1076849305@athlon>

Sorry, my mistake.

When I did a "gdb ./zsh ../core" I noticed it crashed in:

(gdb) bt
#0  0x401eed00 in compctlread () from 
/usr/local/lib/zsh/4.1.1/zsh/compctl.so

And so I realised that compctl is a separate module and not part of the 
zsh executable. (Didn't know this before)

I updated the module, and voilla! It worked.
Sorry for my last mail.

Regards,
Marius.


On 15 Feb 2004, at 14:48, Oliver Kiddle wrote:

> Marius van Wyk wrote:
>> [marius@boa-constructor /home/marius]$ zsh -f
>> boa-constructor% compctl -f -x 'p[2]' -s "`/bin/ls /bin`" --open
>> Segmentation fault (core dumped)
>
> This should fix it.
>
> Index: Src/Zle/compctl.c
> ===================================================================
> RCS file: /cvsroot/zsh/zsh/Src/Zle/compctl.c,v
> retrieving revision 1.16
> diff -u -r1.16 compctl.c
> --- Src/Zle/compctl.c	13 Nov 2003 14:34:38 -0000	1.16
> +++ Src/Zle/compctl.c	15 Feb 2004 12:29:35 -0000
> @@ -857,7 +857,7 @@
>  		}
>  		break;
>  	    default:
> -		if (!first && (**argv == '-' || **argv == '+'))
> +		if (!first && (**argv == '-' || **argv == '+') && !argv[0][1])
>  		    (*argv)--, argv--, ready = 1;
>  		else {
>  		    zwarnnam(name, "bad option: -%c", NULL, **argv);
>
-- 
Director,
Tangible Business Software


      parent reply	other threads:[~2004-02-16 10:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13  7:46 Marius van Wyk
2004-02-15 12:48 ` Oliver Kiddle
2004-02-16 10:21   ` Marius van Wyk
2004-02-16 10:21   ` Marius van Wyk [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=D2609C96-6069-11D8-AF48-000A958FBAFE@e.co.za \
    --to=marius@e.co.za \
    --cc=okiddle@yahoo.co.uk \
    --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).