Re: zsh-3.1.9-dev-6 crashes occassionally

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

Thomas Koehler wrote:

> ...
> 
> > > #0  0x401011cb in free () from /lib/libc.so.6
> > > (gdb) bt
> > > #0  0x401011cb in free () from /lib/libc.so.6
> > > #1  0x40101053 in free () from /lib/libc.so.6
> > > #2  0x807613e in zsfree ()
> > > #3  0x80925e3 in freearray ()
> > > #4  0x807cd66 in arrsetfn ()
> > > #5  0x807cc82 in stdunsetfn ()
> > > #6  0x807cb5a in unsetparam_pm ()
> > > #7  0x807de6d in endparamscope ()
> > > #8  0x8065a49 in scanhashtable ()
> > > #9  0x807dd8f in endparamscope ()
> > > #10 0x8060304 in runshfunc ()
> > > #11 0x4021f682 in comp_setunset () from /usr/lib/zsh/3.1.9-dev-6/zsh/co=
> mple=3D
> > > te.so
> >=20
> > Hm. This seems to suggest that there is some trouble with unsetting
> > the special completion parameters. $words, I guess. We already fixed
> > some problems with it some time ago, but that was before 3.1.9.
> >=20
> > I'll try to stare some more at the code, but can't promise anything.

After looking again: no this is probably not $words, but a normal
array (otherwise it would have called compunsetfn()).

But the whole stack trace shows that his zsh is heavily optimised
(comp_setunset() doesn't call runshfunc()), so this is little or no
help at all.

This is almost certainly a memory corruption problem, something is
writing into memory allocated for a parameter and when that parameter
is freed...

> Could my whole .zshrc be of any help?
> ~> wc -l .zshrc
>     625 .zshrc

Dunno, you can send it to me and I'll give it a try, but I don't know
when I'll find the time.


Bye
 Sven


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