From: anonymous <sup-bugs@masanjin.net>
To: sup-devel@rubyforge.org
Subject: [sup-devel] [issue77] random crash
Date: Fri, 12 Mar 2010 07:28:09 +0000 [thread overview]
Message-ID: <1268378889.12.0.558023869524.issue77@masanjin.net> (raw)
In-Reply-To: <1268378889.12.0.558023869524.issue77@masanjin.net>
New submission from anonymous:
I had just filled in the To address using my external lbdb hook which has always
worked before and sup crashed:
--- NoMethodError from thread: main
undefined method `has_label?' for nil:NilClass
/opt/local/lib/ruby/gems/1.8/gems/sup-0.10.2/lib/sup/modes/thread-index-
mode.rb:237:in `edit_message'
/opt/local/lib/ruby/gems/1.8/gems/sup-0.10.2/lib/sup/hook.rb:55:in `find'
/opt/local/lib/ruby/gems/1.8/gems/sup-0.10.2/lib/sup/thread.rb:81:in `each'
/opt/local/lib/ruby/gems/1.8/gems/sup-0.10.2/lib/sup/thread.rb:170:in
`each_with_stuff'
/opt/local/lib/ruby/gems/1.8/gems/sup-0.10.2/lib/sup/thread.rb:170:in
`each_with_stuff'
/opt/local/lib/ruby/gems/1.8/gems/sup-0.10.2/lib/sup/thread.rb:168:in
`each_with_stuff'
/opt/local/lib/ruby/gems/1.8/gems/sup-0.10.2/lib/sup/thread.rb:170:in
`each_with_stuff'
/opt/local/lib/ruby/gems/1.8/gems/sup-0.10.2/lib/sup/thread.rb:169:in `each'
/opt/local/lib/ruby/gems/1.8/gems/sup-0.10.2/lib/sup/thread.rb:169:in
`each_with_stuff'
/opt/local/lib/ruby/gems/1.8/gems/sup-0.10.2/lib/sup/thread.rb:170:in
`each_with_stuff'
/opt/local/lib/ruby/gems/1.8/gems/sup-0.10.2/lib/sup/thread.rb:169:in `each'
/opt/local/lib/ruby/gems/1.8/gems/sup-0.10.2/lib/sup/thread.rb:169:in
`each_with_stuff'
/opt/local/lib/ruby/gems/1.8/gems/sup-0.10.2/lib/sup/thread.rb:170:in
`each_with_stuff'
/opt/local/lib/ruby/gems/1.8/gems/sup-0.10.2/lib/sup/thread.rb:169:in `each'
/opt/local/lib/ruby/gems/1.8/gems/sup-0.10.2/lib/sup/thread.rb:169:in
`each_with_stuff'
/opt/local/lib/ruby/gems/1.8/gems/sup-0.10.2/lib/sup/thread.rb:170:in
`each_with_stuff'
/opt/local/lib/ruby/gems/1.8/gems/sup-0.10.2/lib/sup/thread.rb:169:in `each'
/opt/local/lib/ruby/gems/1.8/gems/sup-0.10.2/lib/sup/thread.rb:169:in
`each_with_stuff'
/opt/local/lib/ruby/gems/1.8/gems/sup-0.10.2/lib/sup/thread.rb:78:in `each'
/opt/local/lib/ruby/gems/1.8/gems/sup-0.10.2/lib/sup/thread.rb:75:in `each'
/opt/local/lib/ruby/gems/1.8/gems/sup-0.10.2/lib/sup/modes/thread-index-
mode.rb:237:in `find'
/opt/local/lib/ruby/gems/1.8/gems/sup-0.10.2/lib/sup/modes/thread-index-
mode.rb:237:in `edit_message'
/opt/local/lib/ruby/gems/1.8/gems/sup-0.10.2/lib/sup/mode.rb:51:in `send'
/opt/local/lib/ruby/gems/1.8/gems/sup-0.10.2/lib/sup/mode.rb:51:in
`handle_input'
/opt/local/lib/ruby/gems/1.8/gems/sup-0.10.2/lib/sup/buffer.rb:270:in
`handle_input'
/opt/local/lib/ruby/gems/1.8/gems/sup-0.10.2/bin/sup:270
/opt/local/bin/sup:19:in `load'
/opt/local/bin/sup:19
Reminder: to update your Ferret index to Xapian, run sup-convert-ferret-index.
----------
messages: 194
nosy: anonymous
priority: bug
ruby_version: 1.8.7
status: unread
sup_version: 10.2
title: random crash
_________________________________________
Sup issue tracker <sup-bugs@masanjin.net>
<http://masanjin.net/sup-bugs/issue77>
_________________________________________
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
parent reply other threads:[~2010-03-12 7:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1268378889.12.0.558023869524.issue77@masanjin.net>]
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=1268378889.12.0.558023869524.issue77@masanjin.net \
--to=sup-bugs@masanjin.net \
--cc=sup-devel@rubyforge.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