There seems to be something wrong with libeazel-engine.so. On machine 1
(AMD Athlon, 256MB RAM) it will segfault most of the time if you close a
window and then select a new tool. Output of gdb is:
GNU gdb 5.0mdk-11mdk Linux-Mandrake 8.0
Copyright 2001 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 "i386-mandrake-linux"...(no debugging symbols found)...
(gdb) run
Starting program: /usr/bin/gimp
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...
(no debugging symbols found)...[New Thread 1024 (LWP 19239)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 19239)]
0x4046c6c7 in eazel_engine_fill_gradient_rgb_buffer () from
/usr/lib/gtk/themes/engines/libeazel-engine.so
(gdb) bt
#0 0x4046c6c7 in eazel_engine_fill_gradient_rgb_buffer () from
/usr/lib/gtk/themes/engines/libeazel-engine.so
Cannot access memory at address 0xc002df80
(gdb)
On machine 2 (Twin PIII, 512MB) it locks up (100% CPU time) when changing
tools. Gdb shows that it is stuck inside the same routine
(eazel_engine_fill_gradient_rgb_buffer).
Versions:
gimp-1.2.1-5mdk
mandrake_desk-8.0-8mdk
Michael
