Subject: [sup-talk] sup-mail crash

From: [email-masked] (Simon Raven)
Date: Sun, 1 Feb 2009 17:26:23 -0500

attached is the exception log

-- 
"A mouse is a device used to point at the xterm you want to type in"
                -- A.S.R.
-------------- next part --------------
--- 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 377228: <Bad file descriptor>

/usr/lib/ruby/1.8/sup/index.rb:362:in `default'
/usr/lib/ruby/1.8/sup/index.rb:362:in `[]'
/usr/lib/ruby/1.8/sup/index.rb:362:in `build_message'
/usr/lib/ruby/1.8/sup/index.rb:342:in `each_message_in_thread_for'
/usr/lib/ruby/1.8/sup/thread.rb:341:in `call'
/usr/lib/ruby/1.8/sup/thread.rb:341:in `load_thread_for_message'
/usr/lib/ruby/1.8/sup/index.rb:354:in `each_message_in_thread_for'
/usr/lib/ruby/1.8/sup/index.rb:354:in `each'
/usr/lib/ruby/1.8/sup/index.rb:354:in `each_message_in_thread_for'
/usr/lib/ruby/1.8/sup/thread.rb:339:in `load_thread_for_message'
/usr/lib/ruby/1.8/sup/thread.rb:331:in `load_n_threads'
/usr/lib/ruby/1.8/sup/index.rb:263:in `each_id_by_date'
/usr/lib/ruby/1.8/sup/index.rb:263:in `each'
/usr/lib/ruby/1.8/sup/index.rb:263:in `each_id_by_date'
/usr/lib/ruby/1.8/sup/thread.rb:326:in `load_n_threads'
/usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:499:in `__unprotected_load_n_threads'
(eval):12:in `load_n_threads'
/usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:483:in `load_n_threads_background'
/usr/lib/ruby/1.8/sup.rb:84:in `reporting_thread'
/usr/lib/ruby/1.8/sup.rb:82:in `initialize'
/usr/lib/ruby/1.8/sup.rb:82:in `new'
/usr/lib/ruby/1.8/sup.rb:82:in `reporting_thread'
/usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:482:in `load_n_threads_background'
/usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:552:in `__unprotected_load_threads'
(eval):12:in `load_threads'
/usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:76:in `initialize'
/usr/lib/ruby/1.8/sup/modes/line-cursor-mode.rb:177:in `call'
/usr/lib/ruby/1.8/sup/modes/line-cursor-mode.rb:177:in `call_load_more_callbacks'
/usr/lib/ruby/1.8/sup/modes/line-cursor-mode.rb:177:in `each'
/usr/lib/ruby/1.8/sup/modes/line-cursor-mode.rb:177:in `call_load_more_callbacks'
/usr/lib/ruby/1.8/sup/modes/line-cursor-mode.rb:137:in `page_down'
/usr/lib/ruby/1.8/sup/mode.rb:49:in `send'
/usr/lib/ruby/1.8/sup/mode.rb:49:in `handle_input'
/usr/lib/ruby/1.8/sup/buffer.rb:240:in `handle_input'
/usr/bin/sup-mail:187

---

From: [email-masked] (Tomas Pospisek Mailing Lists)
Date: Mon, 09 Feb 2009 23:41:46 +0100

Search the ML archives. This looks similar to other crash reports and
might be the same issue.
*t

On 2/6/2009, "Simon Raven" <simon.raven at gmail.com> wrote:

> ...

---

From: [email-masked] (William Morgan)
Date: Mon, 09 Feb 2009 15:09:37 -0800

> Search the ML archives. This looks similar to other crash reports and

In particular I'm pretty sure this is fixed in git, which I'll be
releasing "any day now".
-- 
William <wmorgan-sup at masanjin.net>

---

From: [email-masked] (Marcus Williams)
Date: Tue, 10 Feb 2009 12:28:08 +0000

> In particular I'm pretty sure this is fixed in git, which I'll be

I've not been able to track sup git on my work machine for a while
because something introduced between 0.6 and latest head has borked
the mbox code. I get an odd hash error about the hash changing whilst
being read or something. Not sure how to track down what causes it
though.

I can probably update and get stack trace if its any use.

Marcus

---

From: [email-masked] (Tomas Pospisek Mailing Lists)
Date: Thu, 12 Feb 2009 00:05:46 +0100

>In particular I'm pretty sure this is fixed in git, which I'll be

Wow. That would be fantastic. I quite liked sup, but it wasn't stable.
And being stable at runtime is about the number #1 feature for any SW
for me.
*t, waiting the day X

---

From: [email-masked] (William Morgan)
Date: Thu, 12 Feb 2009 13:58:20 -0800

> I can probably update and get stack trace if its any use.

Yeah, I'd be interested in this. There are definite mbox problems but I
don't think they are new ones, and they don't involve anything with
hashes AFAIK.
-- 
William <wmorgan-sup at masanjin.net>

---

From: [email-masked] (Rick Tessner)
Date: Thu, 12 Feb 2009 14:21:27 -0800

> don't think they are new ones, and they don't involve anything with

Resending since it looks like I only replied to wmorgan originally ...

I've had this problem occassionally about a "hash modified during
iteration" and I use maildir rather than mbox.

Attached is a patch to fix that problem.

-- 
Rick
rick.tessner at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Fixed-bug-where-exception-would-be-raised-about-hash.patch
Type: application/mbox
Size: 973 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090212/1b62cf21/attachment.bin>

---

From: [email-masked] (William Morgan)
Date: Sun, 22 Mar 2009 10:46:17 -0700

Whoops, I lied. This was the other bugfix I wanted to get in to 0.7.

> Attached is a patch to fix that problem.

Thanks! I've applied an equivalent patch to master:

-    header.each { |k, v| header[k.downcase] = v }
+    header.keys.each { |k| header[k.downcase] = v } # canonicalize

Please let me know if the current master works for you.
-- 
William <wmorgan-sup at masanjin.net>

---

From: [email-masked] (Decklin Foster)
Date: Sun, 22 Mar 2009 20:04:30 -0400

> Please let me know if the current master works for you.

WFM. I was just about to send a patch when I noticed this
thread :)

Debian users, here's a package of master to test:
http://apt.rupamsunyata.org/sup/
I'll just wait for 0.7 to upload something official.
-- 
things change.
decklin at red-bean.com