From: anonymous <sup-bugs@masanjin.net>
To: sup-devel@rubyforge.org
Subject: [sup-devel] [issue46] "stack level too deep" within xapian code
Date: Tue, 19 Jan 2010 18:35:36 +0000 [thread overview]
Message-ID: <1263926136.68.0.119961985085.issue46@masanjin.net> (raw)
In-Reply-To: <1263926136.68.0.119961985085.issue46@masanjin.net>
New submission from anonymous:
In the most recent next, after writing a message:
--- SystemStackError from thread: main
stack level too deep
./lib/sup/xapian_index.rb:600:in `old_add_term'
./lib/sup/xapian_index.rb:600:in `old_add_term'
./lib/sup/xapian_index.rb:600:in `add_term'
./lib/sup/xapian_index.rb:470:in `index_message_static'
./lib/sup/xapian_index.rb:470:in `each'
./lib/sup/xapian_index.rb:470:in `index_message_static'
./lib/sup/xapian_index.rb:474:in `[]'
./lib/sup/xapian_index.rb:474:in `index_message_static'
./lib/sup/xapian_index.rb:442:in `sync_message'
./lib/sup/xapian_index.rb:96:in `add_message'
./lib/sup/index.rb:236:in `send'
./lib/sup/index.rb:236:in `method_missing'
./lib/sup/poll.rb:183:in `add_new_message'
./lib/sup/util.rb:553:in `send'
./lib/sup/util.rb:553:in `method_missing'
./lib/sup/sent.rb:33:in `write_sent_message'
./lib/sup/poll.rb:169:in `each_message_from'
./lib/sup/imap.rb:197:in `each'
./lib/sup/imap.rb:185:in `upto'
./lib/sup/imap.rb:185:in `each'
./lib/sup/util.rb:593:in `send'
./lib/sup/util.rb:593:in `__pass'
./lib/sup/util.rb:580:in `method_missing'
./lib/sup/poll.rb:157:in `each_message_from'
./lib/sup/util.rb:553:in `send'
./lib/sup/util.rb:553:in `method_missing'
./lib/sup/sent.rb:30:in `write_sent_message'
./lib/sup/util.rb:553:in `send'
./lib/sup/util.rb:553:in `method_missing'
./lib/sup/modes/edit-message-mode.rb:325:in `send_message'
./lib/sup/mode.rb:51:in `send'
./lib/sup/mode.rb:51:in `handle_input'
./lib/sup/buffer.rb:272:in `handle_input'
bin/sup:276
----------
messages: 111
nosy: anonymous
priority: bug
ruby_version: 1.8.7
status: unread
sup_version: git next
title: "stack level too deep" within xapian code
_________________________________________
Sup issue tracker <sup-bugs@masanjin.net>
<http://masanjin.net/sup-bugs/issue46>
_________________________________________
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
parent reply other threads:[~2010-01-19 18:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1263926136.68.0.119961985085.issue46@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=1263926136.68.0.119961985085.issue46@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