On 10/19/06, Ilya Grigorik <[EMAIL PROTECTED]> wrote: > Dave, > > 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. > > Ilya
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: http://ferret.davebalmain.com/trac/wiki/DownloadCurrent Cheers, Dave _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
