On Saturday 16 October 2004 20:52, Koos Pol wrote: > >> When pressing 'Save' tuxpaint bails out with: > >> Fatal signal: Segmentation Fault (SDL Parachute Deployed)
Got help from a local Linux group and can now present the following from gdb: [EMAIL PROTECTED]:~> gdb tuxpaint GNU gdb 5.3 Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i586-suse-linux"...(no debugging symbols found)... (gdb) run Starting program: /usr/bin/tuxpaint (no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 2715)] (no debugging symbols found)... (no debugging symbols found)...[New Thread 32769 (LWP 2716)] [New Thread 16386 (LWP 2717)] [New Thread 32771 (LWP 2718)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 2715)] 0x40245d79 in _int_free () from /lib/libc.so.6 (gdb) backtrace #0 0x40245d79 in _int_free () from /lib/libc.so.6 #1 0x40244a5f in free () from /lib/libc.so.6 #2 0x40116369 in png_destroy_struct_2 () from /usr/lib/libSDL_image-1.2.so.0 #3 0x4031bc12 in png_destroy_write_struct () from /usr/lib/libpng12.so.0 (gdb) My helper said that available debug symbols would greatly improve debugging, but apparently they've been stripped. Is this at all helpful in any way? Anything else I can do to help isolate and fix the problem? Thanks, Koos -- 43rd Law of Computing: Anything that can go wr fortune: Segmentation violation -- Core dumped _______________________________________________ Tuxpaint-dev mailing list [EMAIL PROTECTED] http://tux4kids.net/mailman/listinfo/tuxpaint-dev
