Re: bug with completion (after 15 oct?)

[Sven Wischnowsky <wischnow@informatik.hu-berlin.de>]

Geoff Wing wrote:

> Heyla,
> am currently investigating a bug with completion which manifested in the
> last week or so:
> 
> % zsh.new -f
> % cd /tmp; mkdir foo; cd foo; touch bar baz
> % ls ba<TAB>	# <TAB><RETURN> or CTRL-U or whatever
> bar baz
> % ls ba<TAB>	# OK
> % exit
> % zsh.new
> % cd /tmp
> % ls ba<TAB>	# <TAB><RETURN> or CTRL-U or whatever
> --> completing file
> bar   baz
> % ls ba<TAB>
> zsh: 20301 segmentation fault (core dumped)  zsh.new
> 
> A backtrace gives the following - maybe it's useful to someone - but I'll
> try to narrow it down to a set of initialisation options.
> Hmm, what's worse is that a version compiled --disable-dynamic sometimes
> gives a segv a bit later (line 1034).

Sigh. Of course I couldn't reproduce that.

> 0x80af60b in compprintlist (showall=0) at complist.c:1023
> 1023            char **pp = g->ylist;
> (gdb) p *lastg
> $1 = {name = 0x0, prev = 0x0, next = 0x2, flags = 135607944, mcount = 2, 
>   matches = 0x0, lcount = 0, llcount = 1, ylist = 0x8157fc8, ecount = 0, 
>   expls = 0x0, ccount = 0, lexpls = 0x0, lmatches = 0x0, lfmatches = 0x1, 
>   lallccs = 0x0, num = 0, nbrbeg = 0, nbrend = 2, new = 2, dcount = 1, 
>   cols = 6, lins = 0, width = 12, widths = 0x6, totl = 0, shortest = 80, 
>   perm = 0x0}

Does that mean that amatches is garbled at that point?


Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de