From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6274 invoked by alias); 21 Jul 2015 22:07:00 -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: 35845 Received: (qmail 13764 invoked from network); 21 Jul 2015 22:06:58 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.0 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version:content-type; bh=36VIGeEYWEbU7Lt9r39Noh8sGoobTLHP842HGMAKQwY=; b=MtyY6QabHLMlAJz3cd0s+VeQEo0J/uSwWuBaGV/63QnMNpVIcghgSjfXH0Cm/xOvIi m0TBE+NS+tR1aRHVtBs6SC6g2DpmfTX2vHinevofrai8gpICSC8JzrSJVt0eDBHzm6VK 7yMYudd9J8CuurkXX+iCv4zXM2yPx+6dOztnzcBvuq3C2ECbH4ugv2GaVRsGD6qyfjUR ddVMqDj02J2aAB9jFmcHCjP1RqJoi41sYzir7zERuynAiM0dwHb1qFP+QEhw8BDT+n5C rCLm1lDC4Ua2XZpZOSl4AKuCLcrxBxDdHibzbRUKD+MjYL5olguBVOhltWueyPV92zD2 wSFw== X-Gm-Message-State: ALoCoQk6xH+vGo3DbJQs/AUTCsjQu+RRg9RET8dQiHOyZpmhdn9cAPPYUb3vMzvCG8DF2dwF0Idz X-Received: by 10.182.55.9 with SMTP id n9mr7848737obp.31.1437516410118; Tue, 21 Jul 2015 15:06:50 -0700 (PDT) From: Bart Schaefer Message-Id: <150721150646.ZM15273@torch.brasslantern.com> Date: Tue, 21 Jul 2015 15:06:45 -0700 In-Reply-To: <21142543.ltNyFqy7kU@kdudka.brq.redhat.com> Comments: In reply to Kamil Dudka "SIGSEGV in patmatch() -- Fedora bug #1245116" (Jul 21, 6:01pm) References: <21142543.ltNyFqy7kU@kdudka.brq.redhat.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Kamil Dudka , zsh-workers@zsh.org Subject: Re: SIGSEGV in patmatch() -- Fedora bug #1245116 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Jul 21, 6:01pm, Kamil Dudka wrote: } } Unfortunately, I was not successful in reproducing the crash locally, } neither the original reporter was able to trigger it on demand. Hence, } I am sharing it here in case anybody recognized the actual cause just } from the backtrace. It's yet another crash from region highlighting, so you're probably not going to be able to reproduce it without replicating some of the fancy coloring that is applied by packages like oh-my-zsh and/or prezto. Beyond that I don't recognize anything interesting.