From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: Segfault on "task <Tab><Tab>" with zsh 5.0.2
Date: Fri, 13 Sep 2013 12:51:39 +0100 [thread overview]
Message-ID: <20130913125139.63c57968@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <20130913113412.GZ19439@sym.noone.org>
On Fri, 13 Sep 2013 13:34:12 +0200
Axel Beckert <abe@deuxchevaux.org> 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.
pws
next prev parent reply other threads:[~2013-09-13 12:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 22:18 Axel Beckert
2013-09-13 8:37 ` Peter Stephenson
2013-09-13 11:34 ` Axel Beckert
2013-09-13 11:51 ` Peter Stephenson [this message]
2013-09-13 12:24 ` Axel Beckert
2013-09-13 12:36 ` Peter Stephenson
2013-09-13 19:33 ` Pierre Schmitz
2013-09-16 16:17 ` Ivan S. Freitas
2013-09-16 17:18 ` Axel Beckert
2013-09-17 8:56 ` Peter Stephenson
2013-09-17 16:10 ` Segfault on "task <Tab><Tab>" with zsh 5.0.2 (minimal dataset to reproduce the issue found) Axel Beckert
2013-09-17 16:35 ` Axel Beckert
2013-09-17 19:05 ` Peter Stephenson
2013-09-17 20:12 ` Axel Beckert
2013-09-18 3:05 ` Bart Schaefer
2013-09-18 21:50 ` Segfault on "task <Tab><Tab>" with zsh 5.0.2 [PATCH] Axel Beckert
2013-09-19 8:49 ` Peter Stephenson
2013-09-19 14:42 ` Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130913125139.63c57968@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).