On 6/23/06, Marvin Humphrey <[EMAIL PROTECTED]> wrote: > [resending... for some reason, this didn't go through this morning...] > > On Jun 22, 2006, at 7:45 AM, Sergei Serdyuk wrote: > > >> If I were to wish for something in coming Ferret, I'd wish > >> "stability". > >> I am getting seg_faults every other time I am doing this: > > Dave, I see you've done some work with Valgrind, but I'm not sure how > much. To catch errors and memory leaks with KinoSearch, I wrote up a > simple script that runs the whole test suite under Valgrind. The > test suite takes around 15 minutes to run that way instead of 9 > seconds (on the one box where I have Valgrind available), so I only > run it rarely -- always when preparing a release, and sometimes when > debugging new or refactored C code. Some of the code in KinoSearch's > test suite doesn't even produce output; it's just there to exercise > an area where there might be memory problems. > > Do you have something like that going on with Ferret? It's been > extremely helpful for me. I don't think I've seen a single segfault > bug report since KinoSearch was released, though I have missed a > couple memory leaks because the Valgrind output can be a little hard > to interpret (there are a few harmless items in Perl that look like > memory leaks to Valgrind, which makes real leaks harder to spot). >
Hi Marvin, I do use Valgrind. In fact the reason I have been so quiet on the list lately is I've been working really hard on cleaning up the code in Ferret so that I can realease a more stable version. The tool I need to make more use of is gcov. The problem is that some areas of the code just aren't getting exercised enough. Cheers, Dave _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
