Subject: [sup-talk] two sup crashes

From: [email-masked] (John Bent)
Date: Wed, 06 Aug 2008 08:12:41 -0600

I was sending an email and sup crashed.  I restarted, resent the email,
and then it crashed again right after I archived some emails, saved the
index and tried to refresh my screen.  Both errors are below and seem to
be related.

--- EOFError from thread: main
End-of-File Error occured at <except.c>:93 in xraise
Error occured in compound_io.c:137 - cmpdi_read_i
    Tried to read past end of file. File length is <1> and tried to read
to <162169>

/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/draft.rb:38:in
`default'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/draft.rb:38:in `[]'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/draft.rb:38:in
`discard'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:499:in `send'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:499:in
`method_missing'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/resume-mode.rb:36:in
`send_message'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/mode.rb:49:in `send'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/mode.rb:49:in
`handle_input'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/buffer.rb:240:in
`handle_input'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/bin/sup:189
/opt/local/bin/sup:16:in `load'
/opt/local/bin/sup:16

--- IOError from thread: load threads for thread-index-mode
IO Error occured at <except.c>:93 in xraise
Error occured in fs_store.c:293 - fsi_seek_i
	seeking pos 162482: <Bad file descriptor>

/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/index.rb:362:in `default'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/index.rb:362:in `[]'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/index.rb:362:in `build_message'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/index.rb:263:in `each_id_by_date'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/thread.rb:330:in `call'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/thread.rb:330:in `load_n_threads'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/index.rb:263:in `each_id_by_date'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/index.rb:263:in `each'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/index.rb:263:in `each_id_by_date'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/thread.rb:326:in `load_n_threads'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:499:in `__unprotected_load_n_threads'
(eval):12:in `load_n_threads'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:483:in `load_n_threads_background'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup.rb:85:in `reporting_thread'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup.rb:83:in `initialize'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup.rb:83:in `new'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup.rb:83:in `reporting_thread'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:482:in `load_n_threads_background'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:552:in `__unprotected_load_threads'
(eval):12:in `load_threads'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:87:in `reload'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/mode.rb:49:in `send'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/mode.rb:49:in `handle_input'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/buffer.rb:240:in `handle_input'
/opt/local/lib/ruby/gems/1.8/gems/sup-999/bin/sup:189
/opt/local/bin/sup:16:in `load'
/opt/local/bin/sup:16

---

From: [email-masked] (William Morgan)
Date: Wed, 06 Aug 2008 11:23:59 -0700

Reformatted excerpts from John Bent's message of 2008-08-06:
> I was sending an email and sup crashed.  I restarted, resent the
> email, and then it crashed again right after I archived some emails,
> saved the index and tried to refresh my screen.  Both errors are below
> and seem to be related.

Do the same actions work if you restart Sup?

These are both Ferret index corruption errors, which means I can either
debug Ferret, or rewrite Sup to not use it. (I've chosen the latter.)
-- 
William <wmorgan-sup at masanjin.net>

---

From: [email-masked] (John Bent)
Date: Thu, 07 Aug 2008 07:33:12 -0600

> Do the same actions work if you restart Sup?
Yeah it does.

> debug Ferret, or rewrite Sup to not use it. (I've chosen the latter.)
Oh, that's a relief actually.  I also sometimes get what I recognize as
Ferret errors and ignore them since I know you're moving away from it.
I just somehow didn't recognize these.

---

From: [email-masked] (William Morgan)
Date: Thu, 07 Aug 2008 08:18:10 -0700

> > Do the same actions work if you restart Sup?

Then consider yourself lucky!

And do a sup-dump just in case.
-- 
William <wmorgan-sup at masanjin.net>