From: tpo2@sourcepole.ch (Tomas Pospisek ML)
Subject: [sup-talk] bug: reproducable Sup crash, ferret-less rewrite?
Date: Fri, 31 Oct 2008 23:52:45 +0000 [thread overview]
Message-ID: <YILM7EO5.1225497165.2060790.tpo2@192.168.3.7> (raw)
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/sup-talk at rubyforge.org/msg01217.html
[2] http://www.mail-archive.com/sup-talk at rubyforge.org/msg01218.html
[3] http://gitorious.org/projects/sup
next reply other threads:[~2008-10-31 23:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 23:52 Tomas Pospisek ML [this message]
2008-11-01 3:16 ` Christopher Warrington
2008-11-01 22:13 ` Tomas Pospisek ML
2008-11-02 18:30 ` 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=YILM7EO5.1225497165.2060790.tpo2@192.168.3.7 \
--to=tpo2@sourcepole.ch \
/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