On Mon, 2005-01-10 at 14:11, Karl Ove Hufthammer wrote: > OK. I've now run GDB on Tux Paint. Here's the result.
It looks like a crash in FreeType, though the stack is too messed up to be sure. Some random ideas: Ensure that FreeType is compiled with -fno-strict-aliasing or, slower, with -O0. FreeType violates the C standard, which now damn-near prohibits casting pointers. BTW, there are violations in the Tux Paint getpixel/putpixel code too. You can binary search throught the code with printf(). Try compiling Tux Paint and/or the libraries with options to do stack checking. ProPolice is used by DragonFly BSD, OpenBSD, and Hardened Gentoo. http://en.wikipedia.org/wiki/StackGuard http://en.wikipedia.org/wiki/ProPolice http://en.wikipedia.org/wiki/Stack-Smashing_Protector http://www.trl.ibm.com/projects/security/ssp/ Using the ProPolice gcc, I think you'd want to compile with these options: -fno-strict-aliasing -fstack-protector-all -fstack-protector -fno-omit-frame-pointer -ggdb _______________________________________________ Tuxpaint-dev mailing list [email protected] http://tux4kids.net/mailman/listinfo/tuxpaint-dev
