From: jeff.covey@pobox.com (jeff covey)
Subject: [sup-talk] exception on loading more threads
Date: Mon, 18 Jun 2007 07:33:23 -0400 [thread overview]
Message-ID: <1182166294-sup-7610@mona> (raw)
i just started sup, hit "m" to load more threads, and got this:
[Mon Jun 18 07:27:57 -0400 2007] oh crap, an exception
[Mon Jun 18 07:27:57 -0400 2007] unlocking /home/jeff/.sup/lock...
----------------------------------------------------------------
I'm very sorry, but it seems that an error occurred in Sup.
Please accept my sincere apologies. If you don't mind, please
send the backtrace below and a brief report of the circumstances
to sup-talk at rubyforge dot orgs so that I might address this
problem. Thank you!
Sincerely,
William
----------------------------------------------------------------
The problem was: 'IO Error occured at <except.c>:93 in xraise
Error occured in fs_store.c:293 - fsi_seek_i
seeking pos 566286: <Bad file descriptor>
' (error type IOError)
A backtrace follows:
./lib/sup/index.rb:211:in `default': IO Error occured at <except.c>:93 in xraise (IOError)
Error occured in fs_store.c:293 - fsi_seek_i
seeking pos 566286: <Bad file descriptor>
from ./lib/sup/index.rb:211:in `[]'
from ./lib/sup/index.rb:211:in `each_id_by_date'
from ./lib/sup/index.rb:211:in `each'
from ./lib/sup/index.rb:211:in `each_id_by_date'
from ./lib/sup/thread.rb:301:in `load_n_threads'
from ./lib/sup/modes/thread-index-mode.rb:354:in `unsynchronized_load_n_threads'
from (eval):3:in `load_n_threads'
from (eval):3:in `synchronize'
... 8 levels...
from ./lib/sup/mode.rb:52:in `send'
from ./lib/sup/mode.rb:52:in `handle_input'
from ./lib/sup/buffer.rb:178:in `handle_input'
from bin/sup:183
checking for messages to delete...
./lib/sup/util.rb:5: warning: method redefined; discarding old gen_lock_id
./lib/sup/util.rb:16: warning: method redefined; discarding old dump_lock_id
thanks,
--
jeff covey
http://jeffcovey.net/
reply other threads:[~2007-06-18 11:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1182166294-sup-7610@mona \
--to=jeff.covey@pobox.com \
/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