Bryce Harrington wrote:
On Wed, 8 Dec 2004, MenTaLguY wrote:
On Wed, 8 Dec 2004, Carsten Niehaus wrote:
The reasons are that Inkscape is "known" to crash an startup for some people (see e.g. [2]).
A backtrace from gdb (not an strace trace) would be required to diagnose this one. It's either the result of a double free or something attempting to use an uninitialized pointer.
NPTL should not make a difference.
Looking at the strace, it appears to be choking after loading libgimpgrad.so:
access("/usr/bin/gs", F_OK) = 0 access("/usr/lib/inkscape/plugins/libgimpgrad.so", F_OK) = 0 writev(2, [{"*** glibc detected *** ", 23}, {"free(): invalid pointer", 23}, {": 0x0838c460 ***\n", 17}], 3*** glibc detected *** free(): invalid pointer: 0x0838c460 *** ) = 63 rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
Last week we were looking at a very similar issue (on Mandrake IIRC) and traced the issue down to a particular extension (gimpgrad). Ted said this was the only extension that used a loadable library.
http://sourceforge.net/mailarchive/forum.php?thread_id=6091850&forum_id=...
Could people who are able to recreate this bug try deleting the gimpgrad.inx file from their installation and see if that resolves the problem? This file should be located in /usr/share/inkscape/extensions or similar.
Bryce
Hey, this looks familiar!
"free(): invalid pointer", 23}, {": 0x0838c460 ***\n", 17}], 3*** glibc detected *** free(): invalid pointer: 0x0838c460 *** ) = 63
looks almost precisely like the Boehm-GC and DLL problem. Can this be another address space problem between executable and shared object?
And would maybe the -fPIC flag help here?
Bob