From: sup-talk@gurski.org (Michael Gurski)
Subject: [sup-talk] Crash on startup, "wrong id called on nil"
Date: Thu, 7 Feb 2008 12:27:26 -0500 [thread overview]
Message-ID: <20080207172725.GA9157@gurski.org> (raw)
It's been a while since I launched sup, and updating today from
master, I get a crash on startup:
--- RuntimeError from thread: load threads for thread-index-mode
wrong id called on nil
IIRC, this was also happening maybe a month or so ago, and I just
didn't have the time to deal with it then. Dumping the index,
rebuilding, etc, seem to not affect this at all.
The full exception log is:
$ cat sup-exception-log.txt
--- RuntimeError from thread: load threads for thread-index-mode
wrong id called on nil
./lib/sup.rb:13:in `id'
./lib/sup/modes/thread-index-mode.rb:183:in `update'
./lib/sup/hook.rb:123:in `sort_by'
./lib/sup/modes/thread-index-mode.rb:183:in `each'
./lib/sup/modes/thread-index-mode.rb:183:in `sort_by'
./lib/sup/modes/thread-index-mode.rb:183:in `update'
/usr/lib/ruby/1.8/thread.rb:135:in `synchronize'
./lib/sup/modes/thread-index-mode.rb:181:in `update'
./lib/sup/modes/thread-index-mode.rb:466:in
`__unprotected_load_n_threads'
./lib/sup/thread.rb:332:in `load_n_threads'
./lib/sup/index.rb:224:in `each_id_by_date'
./lib/sup/index.rb:224:in `each'
./lib/sup/index.rb:224:in `each_id_by_date'
./lib/sup/thread.rb:326:in `load_n_threads'
./lib/sup/modes/thread-index-mode.rb:463:in
`__unprotected_load_n_threads'
(eval):12:in `load_n_threads'
./lib/sup/modes/thread-index-mode.rb:452:in
`load_n_threads_background'
./lib/sup.rb:60:in `reporting_thread'
./lib/sup.rb:58:in `initialize'
./lib/sup.rb:58:in `new'
./lib/sup.rb:58:in `reporting_thread'
./lib/sup/modes/thread-index-mode.rb:451:in
`load_n_threads_background'
./lib/sup/modes/thread-index-mode.rb:502:in
`__unprotected_load_threads'
(eval):12:in `load_threads'
bin/sup:199
--- SystemExit from thread: main
wrong id called on nil
./lib/sup.rb:64:in `select'
./lib/sup/buffer.rb:31:in `nonblocking_getch'
bin/sup:212
--
Michael A. Gurski (opt. [first].)[last]@pobox.com http://www.pobox.com/~[last]
1024R/39B5BADD PGP: 34 93 A9 94 B1 59 48 B7 17 57 1E 4E 62 56 45 70
1024D/1166213E GPG: 628F 37A4 62AF 1475 45DB AD81 ADC9 E606 1166 213E
4096R/C0B4F04B GPG: 5B3E 75D7 43CF CF34 4042 7788 1DCE B5EE C0B4 F04B
Views expressed by the host do not reflect the staff, management or sponsors.
next reply other threads:[~2008-02-07 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 17:27 Michael Gurski [this message]
2008-02-16 14:27 ` William Morgan
2008-03-17 16:37 ` William Morgan
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=20080207172725.GA9157@gurski.org \
--to=sup-talk@gurski.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