Re: core dump with completion.

[Tanaka Akira <akr@xxxxxxxxxxx>]

In article <990721161435.ZM6916@xxxxxxxxxxxxxxxxxxxxxxx>,
  "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx> writes:

> I can't reproduce this; at least, not in a 3.1.5 static-build tree replacing
> "bin/zsh -f" with "Src/zsh -f".  Maybe it's a dynamic linkage thing.

I retried zsh-3.1.6-test-2 with patches upto 7243 and --disable-dynamic.
But it is reproduced.

In article <9907211549.AA13416@xxxxxxxxxxxxxxxxx>,
  Peter Stephenson <pws@xxxxxxxxxxxxxxxxx> writes:

> Something's happening in _first.  This is a no-op by default, so if you have
> something different it might help to see it.  If not then... er.

_first is not modified. And share/zsh/functions/* are not modified at
all.

#0  0xff136bf8 in strlen ()
(gdb) up
#1  0x6df68 in dupstring (s=0x1 <Address 0x1 out of bounds>) at mem.c:494
494         t = (char *)ncalloc(strlen((char *)s) + 1);
(gdb) up
#2  0x98424 in arrdup (s=0x1a754c) at utils.c:2234
2234        while ((*x++ = dupstring(*s++)));
(gdb) up
#3  0xabf40 in comp_wrapper (list=0x0, w=0x0, name=0x17c770 "_first")
    at compctl.c:2412
2412                owords = arrdup(compwords);
(gdb) print compwords[0]
$1 = 0x162c80 "sh"
(gdb) print compwords[1]
$2 = 0x1a7c10 ""
(gdb) print compwords[2]
$3 = 0x1 <Address 0x1 out of bounds>
(gdb) print compwords[3]
$4 = 0x0
(gdb) 

Hm...
-- 
Tanaka Akira