From: Pierre Schmitz <pierre@archlinux.de>
To: zsh-workers@zsh.org
Subject: Re: Segfault on "task <Tab><Tab>" with zsh 5.0.2
Date: Fri, 13 Sep 2013 21:33:15 +0200 [thread overview]
Message-ID: <fa49a0192d7dd67145dfa34a783ec280@archlinux.de> (raw)
In-Reply-To: <20130913122426.GA19439@sym.noone.org>
Am 13.09.2013 14:24, schrieb Axel Beckert:
> Hi Peter,
>
> On Fri, Sep 13, 2013 at 09:37:32AM +0100, Peter Stephenson wrote:
>> Looks like a memory error. Does valgrind give any extra hints?
>
> On Fri, Sep 13, 2013 at 12:51:39PM +0100, Peter Stephenson wrote:
>> 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.
>
> Ah, did you mean malfunctioning RAM as in "hardware defect"?
>
> But shouldn't it be then less easy to reproduce as different memory
> areas should be in use when trying it a day later or so?
>
> The machine is a Xen DomU virtual machine btw. -- not sure if that
> makes a difference here.
Seems like some people have a similar or the same problem though:
https://bugs.archlinux.org/task/35736
--
Pierre Schmitz, https://pierre-schmitz.com
next prev parent reply other threads:[~2013-09-13 19:40 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
2013-09-13 12:24 ` Axel Beckert
2013-09-13 12:36 ` Peter Stephenson
2013-09-13 19:33 ` Pierre Schmitz [this message]
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=fa49a0192d7dd67145dfa34a783ec280@archlinux.de \
--to=pierre@archlinux.de \
--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).