Thanks for your bug report. Could you try to get a valgrind log for the
crash (you can follow the instructions on
https://wiki.ubuntu.com/Valgrind)?
** Changed in: gtk+2.0 (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Ubuntu Desktop Bugs
Status: New = Incomplete
The crash is forced by elecrric-fence, presumably as a way to get a
back-trace when running inside a debugger.
valgrind on its own does not complain about anything related (mostly
just unitialised bytes in various X11 writes).
valgrind with electric-fence doesn't work, as valgrind hasn't been
Please close as invalid,
The bug is in electric-fence. Since it doesn't replace posix_memalign,
it doesn't track memory allocations made by glib's slice allocator.
These are than free'd with free(), as glibc allows.
I've worked (hacked) around it locally, and (if time permits) will
forward some
closing the bug
** Changed in: gtk+2.0 (Ubuntu)
Status: Incomplete = Invalid
--
gtk memory corruption found with electric-fence
https://bugs.launchpad.net/bugs/131740
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
backtrace from electric-fence's complaint in evolution:
Core was generated by `evolution'.
Program terminated with signal 4, Illegal instruction.
#0 0xe410 in ?? ()
(gdb) bt
#0 0xe410 in ?? ()
#1 0xbfd8ba58 in ?? ()
#2 0xb7f52278 in ?? () from /usr/lib/libefence.so
#3 0x0004 in
backtrace from gschem linked against electric-fence directly
Electric Fence 2.1 Copyright (C) 1987-1998 Bruce Perens.
gEDA/gschem version 1.1.1.20070708
gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more details.
This is free software, and you are welcome to redistribute it
