From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.155.88 with SMTP id r24cs129314bkw; Tue, 20 Jul 2010 12:31:17 -0700 (PDT) Received: by 10.231.160.17 with SMTP id l17mr7357056ibx.102.1279654275601; Tue, 20 Jul 2010 12:31:15 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id x7si14199604ibd.70.2010.07.20.12.31.15; Tue, 20 Jul 2010 12:31:15 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-devel-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-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id C962418583AE; Tue, 20 Jul 2010 15:31:14 -0400 (EDT) X-Greylist: delayed 347 seconds by postgrey-1.31 at rubyforge.org; Tue, 20 Jul 2010 15:21:28 EDT Received: from li162-130.members.linode.com (li162-130.members.linode.com [173.230.152.130]) by rubyforge.org (Postfix) with ESMTP id C23421858363 for ; Tue, 20 Jul 2010 15:21:28 -0400 (EDT) Received: by li162-130.members.linode.com (Postfix, from userid 1000) id C368989FE; Tue, 20 Jul 2010 19:15:40 +0000 (UTC) From: Eric Gerlach To: sup-devel Date: Tue, 20 Jul 2010 15:15:40 -0400 Message-Id: <1279653097-sup-8302@gerlach.ca> User-Agent: Sup/0.11 Subject: [sup-devel] Crash, getting "wrong id on nil" when loading new messages X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion 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-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org I get the following crash when loading more messages (at a certain point). I've created an issue for it (111), but I'd like some help debugging this further. I'm pretty sure it's caused by some sort of problematic message in my Maildir, but I don't know which one. I'm pretty good with Ruby, but not so much with the sup codebase. I've traced it down to ThreadIndexMode#update, particularly the part where it calls t.first.id. I've used ruby-debug to be able to isolate the particular thread, and the thread has no children, but then I don't quite know what to do from there. How can I trace a thread object back to its origins? Help? Cheers, Eric wrong id called on nil /var/lib/gems/1.8/gems/sup-0.11/lib/sup.rb:19:in `id' /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:226:in `update' /var/lib/gems/1.8/gems/sup-0.11/lib/sup/hook.rb:55:in `sort_by' /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:226:in `each' /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:226:in `sort_by' /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:226:in `update' /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:224:in `synchronize' /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:224:in `update' /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:642:in `__unprotected_load_n_threads' (eval):12:in `load_n_threads' /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:614:in `load_n_threads_background' /var/lib/gems/1.8/gems/sup-0.11/lib/sup.rb:74:in `reporting_thread' /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:613:in `load_n_threads_background' /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:684:in `__unprotected_load_threads' (eval):12:in `load_threads' /var/lib/gems/1.8/gems/sup-0.11/lib/sup/mode.rb:59:in `send' /var/lib/gems/1.8/gems/sup-0.11/lib/sup/mode.rb:59:in `handle_input' /var/lib/gems/1.8/gems/sup-0.11/lib/sup/buffer.rb:279:in `handle_input' /var/lib/gems/1.8/gems/sup-0.11/bin/sup:279 /var/lib/gems/1.8/bin/sup:19:in `load' /var/lib/gems/1.8/bin/sup:19 _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel