I'm not a heavy user of gimp, but I've noticed it segfaulting regularly
(e.g. when saving, adjusting colours) whenever I've tried using it in the
last couple of weeks or more. Having updated my amd64 snapshot + packages
this morning to I'm still seeing problems. Here's an example backtrace from
github which suggests the problem might be in bable? I wonder if anyone else
has seen this problem, or has any idea what it might be (or what might have
caused it)?
Program received signal SIGSEGV, Segmentation fault.
[Switching to thread 523403]
0x00000445260f63ec in rgbaf_to_Labaf_sse2 ()
from /usr/local/lib/babl-0.1/x86-64-v3-CIE.so
(gdb) bt
#0 0x00000445260f63ec in rgbaf_to_Labaf_sse2 ()
from /usr/local/lib/babl-0.1/x86-64-v3-CIE.so
#1 0x00000444488ef45c in babl_fish_lut_process_maybe ()
from /usr/local/lib/libbabl-0.1.so.1.8
#2 0x00000444488eddab in babl_fish_path_process ()
from /usr/local/lib/libbabl-0.1.so.1.8
#3 0x00000444488ee04c in babl_process_rows ()
from /usr/local/lib/libbabl-0.1.so.1.8
#4 0x0000044526c67852 in gegl_buffer_iterate_read_simple ()
from /usr/local/lib/libgegl-0.4.so.0.5
#5 0x0000044526c6626d in gegl_buffer_iterate_read_dispatch ()
from /usr/local/lib/libgegl-0.4.so.0.5
#6 0x0000044526c625ed in _gegl_buffer_get_unlocked ()
from /usr/local/lib/libgegl-0.4.so.0.5
#7 0x0000044526c6a05b in load_rects () from /usr/local/lib/libgegl-0.4.so.0.5
#8 0x0000044526c69e82 in gegl_buffer_iterator_next ()
from /usr/local/lib/libgegl-0.4.so.0.5
#9 0x0000044526ca4751 in thread_process ()
from /usr/local/lib/libgegl-0.4.so.0.5
#10 0x0000044526c45c10 in gegl_parallel_distribute_area_func ()
from /usr/local/lib/libgegl-0.4.so.0.5
#11 0x0000044526c45d90 in gegl_parallel_distribute_thread_func ()
from /usr/local/lib/libgegl-0.4.so.0.5
#12 0x00000444452ba715 in g_thread_proxy ()
---Type <return> to continue, or q <return> to quit---
from /usr/local/lib/libglib-2.0.so.4201.8
#13 0x0000044448b05a01 in _rthread_start (v=Unhandled dwarf expression opcode
0xa3
)
at /usr/src/lib/librthread/rthread.c:96
#14 0x00000444f396197a in __tfork_thread ()
at /usr/src/lib/libc/arch/amd64/sys/tfork_thread.S:84
#15 0x00000444f396197a in __tfork_thread ()
at /usr/src/lib/libc/arch/amd64/sys/tfork_thread.S:84
Previous frame identical to this frame (corrupt stack?)
(gdb)
I don't rule out that I'm doing something stupid, though I must admit that
I'm not sure what that might be!
Laurie
