From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4708 invoked by alias); 13 Sep 2013 12:02:10 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 31720 Received: (qmail 23012 invoked from network); 13 Sep 2013 12:01:58 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI, SPF_HELO_PASS autolearn=ham version=3.3.2 Received-SPF: none (ns1.primenet.com.au: domain at samsung.com does not designate permitted sender hosts) X-AuditID: cbfec7f5-b7ef66d00000795a-eb-5232fc4c49f7 Date: Fri, 13 Sep 2013 12:51:39 +0100 From: Peter Stephenson To: zsh-workers@zsh.org Subject: Re: Segfault on "task " with zsh 5.0.2 Message-id: <20130913125139.63c57968@pwslap01u.europe.root.pri> In-reply-to: <20130913113412.GZ19439@sym.noone.org> References: <20130912221812.GY19439@sym.noone.org> <20130913093732.25326b25@pwslap01u.europe.root.pri> <20130913113412.GZ19439@sym.noone.org> Organization: Samsung Cambridge Solution Centre X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu) MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFuplluLIzCtJLcpLzFFi42I5/e/4ZV2fP0ZBBruXKFkcbH7I5MDoserg B6YAxigum5TUnMyy1CJ9uwSujO4v/5gLVnBVnLq3nKWBcR9HFyMnh4SAicTv3iYmCFtM4sK9 9WxdjFwcQgJLGSX+r3jPDOEsZ5JoO7KYFaSKRUBV4sD6PjCbTcBQYuqm2YwgtoiAuMTZtedZ QGxhAUuJ7o1nwOK8AvYSe+9sB6vnFDCW2PTuIzOILSQwkVHi91ewen4BfYmrfz9BXWEvMfMK TK+gxI/J98BqmAW0JDZva2KFsOUlNq95yzyBUWAWkrJZSMpmISlbwMi8ilE0tTS5oDgpPddI rzgxt7g0L10vOT93EyMkCL/uYFx6zOoQowAHoxIPb0eMUZAQa2JZcWXuIUYJDmYlEd5Zd4FC vCmJlVWpRfnxRaU5qcWHGJk4OKUaGKe0v7yTwflj6Rs1vYk72ufuZP7Zrm3FF3//ktdpy/Q+ i0imli03ItS7NC9tcc0J/XjqZPunnSvXxcQa3Zy0zTJGvunmB+/UpCzNXSf11X00ihoFJwZw XD8rXNGd1Bv+NEfu5kM3Y+magJO7wnJ/J5vcXV8Zeczk2No5f4yyHro3qoRNOPg9UYmlOCPR UIu5qDgRANs3jikgAgAA On Fri, 13 Sep 2013 13:34:12 +0200 Axel Beckert 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