From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.92.18 with SMTP id p18cs155902agb; Tue, 6 Oct 2009 09:15:59 -0700 (PDT) Received: by 10.224.101.79 with SMTP id b15mr1518512qao.66.1254845759512; Tue, 06 Oct 2009 09:15:59 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 16si8734813qyk.20.2009.10.06.09.15.59; Tue, 06 Oct 2009 09:15:59 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 3134918582D2; Tue, 6 Oct 2009 12:15:59 -0400 (EDT) Received: from mail-fx0-f210.google.com (mail-fx0-f210.google.com [209.85.220.210]) by rubyforge.org (Postfix) with ESMTP id 2DA3A1858249 for ; Tue, 6 Oct 2009 12:15:50 -0400 (EDT) Received: by fxm6 with SMTP id 6so3967536fxm.19 for ; Tue, 06 Oct 2009 09:15:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:content-type:subject:from:to :in-reply-to:references:date:message-id:user-agent :content-transfer-encoding; bh=RyXdueeGmnhEUYGQ4jDCkiEkn9xKwbQoW6aONvAj4Ig=; b=QOKhPM7DvcBJKJM40TogRSr8F3SfqHUhyQ/GhhiTZOWlbBRlf0U/HsrA9CU/9HY1GO pUYR3trLbwZdpColNsZw60UHAUXQoYqqY0rys8TV9DFSMZ5DhNR9Ob8rWG79eGIrzYXn q+Cs2XLRDHHGRuWXFg+DOc3CcY2UK+8070kfU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:subject:from:to:in-reply-to:references:date:message-id :user-agent:content-transfer-encoding; b=bzKsXqJkb7wxom0m8NDypOVV3pzYCpx3XI/E3Ahnx22EW456XsU/dZuGHb6SSZk8qZ RFZprmuZYD7lgS79ZwhnpVuIltLTFkPCWvDKziUkv4kq/cLvdwxT/CgNHTHSgwEPNprf iFi+RoAbjphAFdnmte9nHvOF0E5sxiu6oxQnA= Received: by 10.103.48.19 with SMTP id a19mr788009muk.136.1254845749400; Tue, 06 Oct 2009 09:15:49 -0700 (PDT) Received: from localhost (physnat56.physics.umass.edu [128.119.50.56]) by mx.google.com with ESMTPS id j9sm375975mue.26.2009.10.06.09.15.48 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 06 Oct 2009 09:15:48 -0700 (PDT) From: Ben Gamari To: sup-talk In-reply-to: <1254844166-sup-1028@ben-laptop> References: <1254844050-sup-4148@ben-laptop> <1254844166-sup-1028@ben-laptop> Date: Tue, 06 Oct 2009 12:15:46 -0400 Message-Id: <1254845543-sup-9458@ben-laptop> User-Agent: Sup/git Subject: Re: [sup-talk] Crash while in thread-view-mode X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Excerpts from Ben Gamari's message of Tue Oct 06 11:53:18 -0400 2009: > Well, it seems like whatever caused the crash earlier did something to > my index. Now any attempt to open a thread-index-mode of my LKML label > (which I was viewing in the earlier crash) causes the client to > immediately crash. > Hmm, it seems like the problem is spreading. I now come to find out that another label triggers this same crash (although I guess it's possible that the intersection of the two labels is non-nil). I tried running a sup-sync -oc on the relevant sources to no avail. I really don't have time to devote to debugging this at the moment so it looks like I might need to take another hiatus from sup. Just as I was starting to get used to it... sigh. Anyways, if anyone has any ideas for improving things, let me know. Thanks! - Ben _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk