Re: zsh 4.2.0 dumping core on completion attempt

[Felix Rosencrantz <f_rosencrantz@yahoo.com>]

One thing that would help others to reproduce your problem is to provide a
minimal "zsh -f" cut&paste script that reproduces the problem.   It would even
be better if you can include a stack trace from your core dumps, or a valgrind
report.   All these will  make it much easier for the folks who might fix the
bug to find the problem.

Here is a possible start of such a script:
zsh -f
autoload -U compinit; compinit -C
zstyle ':completion:*' matcher-list 'm:[-._]=[-._] r:|[-./_]=**'
mkdir bug ; cd bug
touch a_f .foo .bar_foo .foo_bar bar.foo.fez
ls _f<TAB>
<CORE DUMP>


Note that matching specs depend on the possible completion matches.  So try to
find a minimal set of files to touch, that cause the core dump you see.  I
tried your spec, and didn't get a core dump.

Also, there could be other things in your .zshrc that are related to this bug. 
The "-f" flag will prevent your .zshrc from being read.

If you can reproduce it with a "zsh -f" script, then others will too.

Thanks
-FR.


--- Thorsten Kampe <thorsten@thorstenkampe.de> wrote:
> zsh 4.2.0 dumps core under Cygwin and Linux with these lines in my
> .zshrc:
> 
> autoload -U compinit; compinit -C   # completion system
> # case-insensitive and partial-word then substring
> zstyle ':completion:*' matcher-list 'm:{a-zA-Z}={A-Za-z} m:[-._]=[-._]
> r:|[-./_]=** r:|=*' '+l:|=*'
> 
> More precisely it's the "m:[-._]=[-._] r:|[-./_]=**" part.
> 
> (These are variations from "6.7 Matching control and controlling where
> things are inserted" of the User's Guide)
> 
> Surpringly ".f<TAB>" and "_f<TAB>" make zsh dump core while "-f<TAB>"
> and "/f<TAB>" do not. The "f" letter can be in fact any *lower case*
> letter while "_F<TAB>" or ".H<TAB>" don't make zsh dump core.
> 
> Thorsten
> 


	
		
__________________________________
Do you Yahoo!?
Friends.  Fun.  Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/