Subject: [sup-talk] imap-related crash

From: [email-masked] (Ian Taylor)
Date: Fri, 14 Dec 2007 05:34:16 -0500

I glanced over at sup and saw this instead. It was sprawled out over the
screen in the way curses apps do when they output stuff via
stdout/stderr. No sup-exception.txt seemed to be generated.

/usr/lib/ruby/1.8/net/imap.rb:932:in `close': closed stream (IOError)
from /usr/lib/ruby/1.8/net/imap.rb:932:in `receive_responses'
from /usr/lib/ruby/1.8/net/imap.rb:923:in `initialize'
from /usr/lib/ruby/1.8/net/imap.rb:922:in `start'
from /usr/lib/ruby/1.8/net/imap.rb:922:in `initialize'
from /var/lib/gems/1.8/gems/sup-0.3/lib/sup/imap.rb:221:in `new'
from /var/lib/gems/1.8/gems/sup-0.3/lib/sup/imap.rb:221:in `unsafe_connect'
from /var/lib/gems/1.8/gems/sup-0.3/lib/sup/imap.rb:218:in `initialize'
from /var/lib/gems/1.8/gems/sup-0.3/lib/sup/imap.rb:218:in `new'
... 15 levels...
from /var/lib/gems/1.8/gems/sup-0.3/bin/sup:174:in `each'
from /var/lib/gems/1.8/gems/sup-0.3/bin/sup:174
from /var/lib/gems/1.8/bin/sup:16:in `load'
from /var/lib/gems/1.8/bin/sup:16
/usr/lib/ruby/1.8/net/imap.rb:932:in `close': closed stream (IOError)
from /usr/lib/ruby/1.8/net/imap.rb:932:in `receive_responses'
from /usr/lib/ruby/1.8/net/imap.rb:923:in `initialize'
from /usr/lib/ruby/1.8/net/imap.rb:922:in `start'
from /usr/lib/ruby/1.8/net/imap.rb:922:in `initialize'
from /var/lib/gems/1.8/gems/sup-0.3/lib/sup/imap.rb:221:in `new'
from /var/lib/gems/1.8/gems/sup-0.3/lib/sup/imap.rb:221:in `unsafe_connect'
from /var/lib/gems/1.8/gems/sup-0.3/lib/sup/imap.rb:218:in `initialize'
from /var/lib/gems/1.8/gems/sup-0.3/lib/sup/imap.rb:218:in `new'
... 15 levels...
from /var/lib/gems/1.8/gems/sup-0.3/bin/sup:174:in `each'
from /var/lib/gems/1.8/gems/sup-0.3/bin/sup:174
from /var/lib/gems/1.8/bin/sup:16:in `load'
from /var/lib/gems/1.8/bin/sup:16

-- 
Ian Taylor

---

From: [email-masked] (William Morgan)
Date: Tue, 18 Dec 2007 20:45:01 -0800

> from /var/lib/gems/1.8/gems/sup-0.3/lib/sup/imap.rb:218:in `new'

Bizarre. Those lines are definitely in the context of a "rescue
Exception" block. Typically when something nonsensical like this
happens, it's because Net::IMAP is playing with threads and exceptions,
but it's hard to figure out without the full exception.

So, I don't have a good answer for this...

-- 
William <wmorgan-sup at masanjin.net>