Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

Re: Segfault on "task <Tab><Tab>" with zsh 5.0.2

On Fri, 13 Sep 2013 13:34:12 +0200
Axel Beckert <abe@xxxxxxxxxxxxxxx> wrote:
> Not sure if used valgrind properly, but it looks as if it found
> something:
> ==6722== Syscall param capget(data) points to unaddressable byte(s)
> ==6722==    at 0x584AD77: capget (syscall-template.S:81)
> ==6722==    by 0x4E34902: cap_init (in /lib/x86_64-linux-gnu/libcap.so.2.22)
> ==6722==    by 0x4E34995: cap_get_proc (in /lib/x86_64-linux-gnu/libcap.so.2.22)

Might not be related, but it's hard to be sure --- if there is bad
memory around, the completion system has a good chance of being the part
that falls over it.  cap_get_proc() is a library call with no arguments,
but it does do allocation --- if you have zsh's own memory allocation
built in there might be some incompatbility.  It's not entirely clear
there's a real problem here, however.

> ==6722==    at 0x7FF2E8C: freecvdef (in /usr/lib/x86_64-linux-gnu/zsh/5.0.2/zsh/computil.so)
> ==6722==    by 0x7FF68A3: bin_compvalues (in /usr/lib/x86_64-linux-gnu/zsh/5.0.2/zsh/computil.so)

That certainly looks like what's causing the crash, though it's
basically the same information as the backtrace.  I was vaguely hoping
valgrind might have some idea if the memory had already been freed, or
something like that.

Thanks for looking.


Messages sorted by: Reverse Date, Date, Thread, Author