I can reproduce now the following: "Sending... /var/lib/gems/1.8/gems/sup-0.6/lib/sup/index.rb:367: [BUG] Segmentation fault ruby 1.8.6 (2007-09-24) [x86_64-linux] Aborted"
Googling around showed me a similar problem [1] and particulary an enigmatic answer [2] by William Morgan: "These are both Ferret index corruption errors, which means I can either debug Ferret, or rewrite Sup to not use it. (I've chosen the latter.)" I can not find any trace of the latter, i.e. Sup's source code repository at Gitorious [3] doesn't show any ferret amputation. Are you, William Morgan working on a Sup version that doesn't show that supposedly ferret induced crashiness? Possibly your "private" branch is not ready yet and not accessible? *t [1] http://www.mail-archive.com/[email protected]/msg01217.html [2] http://www.mail-archive.com/[email protected]/msg01218.html [3] http://gitorious.org/projects/sup _______________________________________________ sup-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/sup-talk
