From: Eric Gerlach <eric+sup-devel@gerlach.ca>
To: sup-devel <sup-devel@rubyforge.org>
Subject: [sup-devel] Crash, getting "wrong id on nil" when loading new messages
Date: Tue, 20 Jul 2010 15:15:40 -0400 [thread overview]
Message-ID: <1279653097-sup-8302@gerlach.ca> (raw)
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
next reply other threads:[~2010-07-20 19:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 19:15 Eric Gerlach [this message]
2010-07-20 19:37 ` Ben Walton
2010-07-20 20:11 ` Eric Gerlach
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=1279653097-sup-8302@gerlach.ca \
--to=eric+sup-devel@gerlach.ca \
--cc=sup-devel@rubyforge.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox