[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [sup-talk] Crash, bad index, and ensuing misery

To: "Sup-talk@rubyforge.org" <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Crash, bad index, and ensuing misery
From: Guillaume Quintard <guillaume.quintard@gmail.com>
Date: Sat, 3 Oct 2009 23:06:36 +0200
Authentication-results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com
Delivered-to: eg@gaute.vetsj.com
Delivered-to: sup-talk@rubyforge.org
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=HQZfS9tGs5WQdxv6ct5qSqTA6FtMOhEoM6V1Iu+yW3U=; b=toqFvsn8qV9B0cJrcAkDBLnPSDrsKoVgKI62i7q/j721dd6flu/UzrVbP+TFeBqnmk ASehS5We/8fFx9HLJUJcFd3knZ2pHq3OCE4iqCXo5LNE65lq9bNkkh1nGRThYy/nEXAm 7/L9mQi3tsyvMdDZCgZWM5hFhFKClxaHVttns=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=fPzxfACLbY2qfqc/xiS9xCthVOBFe5LUCUO6QV5zu8okOWBZG4AdWYjU4rWtAz+Nbl 9AC+t73HZwqhhM/P8LnZDu2DBpnq7zNKU4xgCYrqH+StpzQfuug9xPHR/LwGV3ywjlqj VMdxaBl4uzGEQ4dvrWA6R4jPtwvY1yTe77qLQ=
In-reply-to: <1254600926-sup-5190@zyrg.net>
List-archive: <http://rubyforge.org/pipermail/sup-talk>
List-help: <mailto:sup-talk-request@rubyforge.org?subject=help>
List-id: User & developer discussion of Sup <sup-talk.rubyforge.org>
List-post: <mailto:sup-talk@rubyforge.org>
List-subscribe: <http://rubyforge.org/mailman/listinfo/sup-talk>, <mailto:sup-talk-request@rubyforge.org?subject=subscribe>
List-unsubscribe: <http://rubyforge.org/mailman/options/sup-talk>, <mailto:sup-talk-request@rubyforge.org?subject=unsubscribe>
References: <1e5fdab70910031304g255a9d13v4dc99400def375a5@mail.gmail.com> <1254600926-sup-5190@zyrg.net>
Sender: sup-talk-bounces@rubyforge.org

On Sat, Oct 3, 2009 at 10:17 PM, Rich Lane <rlane@club.cc.cmu.edu> wrote:
> I'd hoped this kind of corruption wouldn't be possible with newer
> xapian-index versions. What sup commit are you on? What version of
> Xapian are you using? Which Xapian backend, Flint or Chert?
>

ubuntu 9.10
libxapian-ruby1.8    1.0.14-1
I'd say flink since I often have to remove flintlock after sup
commiting suicide.

and git status says
# On branch next
# Your branch is ahead of 'origin/next' by 6 commits.

(ahead?)

-- 
Guillaume
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

Follow-Ups:
- Re: [sup-talk] Crash, bad index, and ensuing misery
  - From: Rich Lane <rlane@club.cc.cmu.edu>
- Re: [sup-talk] Crash, bad index, and ensuing misery
  - From: Olly Betts <olly@survex.com>

References:
- [sup-talk] Crash, bad index, and ensuing misery
  - From: Guillaume Quintard <guillaume.quintard@gmail.com>
- Re: [sup-talk] Crash, bad index, and ensuing misery
  - From: Rich Lane <rlane@club.cc.cmu.edu>

Prev by Date: [sup-talk] next search in buffer view..
Next by Date: Re: [sup-talk] Crash, bad index, and ensuing misery
Previous by thread: Re: [sup-talk] Crash, bad index, and ensuing misery
Next by thread: Re: [sup-talk] Crash, bad index, and ensuing misery
Index(es):
- Date
- Thread