[Bug] Seg Faulting in index.rb:718


Ferret is repeatedly seg-faulting my mongrel servers on the same line:

[BUG] Segmentation fault
ruby 1.8.5 (2006-08-25) [i686-linux]

I’m using ferret 0.10.11. I haven’t had the time to dig into yet, it’s
on the backburner right now - I just keep several spare servers and
restart them periodically but maybe someone else can spot the problem.


On 10/19/06, Ilya G. [email protected] wrote:

restart them periodically but maybe someone else can spot the problem.
Hi Ilya,

I’m afraid that isn’t much help since the error is occuring during a
call to search, meaning the segfault could be happening on any one of
50,000 lines of the C code. My first suggestion would be reindexing.
If the index was built with a previous version of Ferret then that
could possibly be the problem. Otherwise, if you can work out how to
reproduce it consistently I’ll be happy to ssh onto your server and
attempt to fix the problem. Let me know how you go.



I’ve just rebuilt the index - I’ll let you know if that helps at all.
But, since the line number doesnt give us anything, do you have any tips
for tracking down the problem? I can’t seem to reproduce the error
myself so I’m simply pulling the Seg Fault messages from my mongrel.log

  • which doesn’t give much aside from the actual Seg Fault error. I’ve
    been trying to correlate the seg faults with my production.log, but so
    far, no luck.


On 10/19/06, Ilya G. [email protected] wrote:

You could try recompiling Ferret with the option -dH (as long as you
are using gcc). This will cause Ferret to dump core when it segfaults.
You can then use gdb to try and find the error or email me the core
dump. There are instructions for building your own gem here:



This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs