Re: [Devel] gnome browsers segfault

[Masatake YAMATO]

> With --trace-children=yes also added I ran valgrind 2.1.1 (stable version
> 2.0.0 doesn't know about --tool=memcheck).
> 
> Galeon and epiphany caused various strange gnome errors and segfault
> even with freetype 2.1.7. Valgrind most likely isn't a perfect tool :-))
> But mozilla was okay, behaved the same way (only much slower) as without
> valgrind.
> 
> The output of valgrind mozilla (both with ft 2.1.7 and 2.1.8) is at the
> usual place:
> http://www.cs.bme.hu/~egmont/freetype/

I have one question. 

valgrind-mozilla-with-ft-2.1.7:

    ==29470== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 21 from 1)
    ==29470== malloc/free: in use at exit: 0 bytes in 0 blocks.
    ==29470== malloc/free: 0 allocs, 0 frees, 0 bytes allocated.
    ==29470== For counts of detected errors, rerun with: -v
    ==29470== No malloc'd blocks -- no leaks are possible.

Is mozilla(with freetype-2.1.8 and valgrind) finally crashed?