Description of problem: stacktrace from gdb attached Version-Release number of selected component (if applicable): gcc-4.1.0-0.29 kernel-2.6.15-1.1969_FC5 openoffice.org-xsltfilter-2.0.1.1-11.2.2 xerces-j2-2.6.2-6jpp_5fc How reproducible: everytime Steps to Reproduce: 1. install openoffice.org-xsltfilter 2. start writer 3. "export" to xhtml Actual results: *boom* Expected results: Additional info: /usr/sbin/sestatus SELinux status: enabled SELinuxfs mount: /selinux Current mode: permissive Mode from config file: permissive Policy version: 20 Policy from config file: targeted
Created attachment 124956 [details] stacktrace of gdb /usr/lib/openoffice.org2.0/program/soffice.bin
I wonder if this is the same as bug 180637
Does soffice.bin link against libgcj.so or it dlopens it? #180637 is supposed to be fixed, libgcj.so now exports pthread_create that should override pthread_create from libpthread.so.
It dlopens it.
I don't think this is the same as 180637, but its related. From looking at the stack trace, it appears this thread was never registered with the GC. This was a known problem previously, and it should have been fixed by this patch: 2006-02-06 Jakub Jelinek <jakub> Anthony Green <green> Tom Tromey <tromey> * include/gc_ext_config.h.in: Added GC_PTHREAD_SYM_VERSION. * include/gc_config.h.in: Rebuilt. * include/gc_pthread_redirects.h (pthread_create): Conditionally define. * pthread_support.c (pthread_create_): New global. (constr): New function. (pthread_create): Conditionally renamed. * configure: Rebuilt. * configure.ac (GC_PTHREAD_SYM_VERSION): Define. So, either you don't have this patch or its not working for OO.org for some reason. bug 180637, on the other hand, was _caused_ by this patch - it occurs when a native, non-Java thread changes the signal mask to block the GC's suspend signal - so you'll get a hang, not a SIGABRT. Either way, the fix for bug 180637 that I'm working on should fix this as well.
*** Bug 183892 has been marked as a duplicate of this bug. ***
The java code in question uses t = new Thread(){... t.start() from java code run in a jvm from a dlopened libgcj. I guess this isn't going to get fixed for FC5 ?
If this is still happening in FC5 then bug #183892 probably wasn't a duplicate, because it's gone away. On a clean FC5 installation yesterday, the letter wizard worked fine.
I have a patch that I think should fix this, but I have yet to build it in to the FC5 libgcj and test OO.org. I'm working on this today and I'll let you know how it goes.
gcc41-java-gc-thread-attach-2.patch, in the GCC bugzilla, should fix this: http://gcc.gnu.org/PR13212
*** Bug 187866 has been marked as a duplicate of this bug. ***
*** Bug 187928 has been marked as a duplicate of this bug. ***
*** Bug 188190 has been marked as a duplicate of this bug. ***
Should be fixed in gcc-4.1.0-6 in rawhide (thanks Bryce). Let's test it now on all arches.
most excellent
*** Bug 189860 has been marked as a duplicate of this bug. ***
was this not pushed as a FC5 update yet ?
No, the amount of gcc bugreports is still quite high and thus more bugs should accumulate before FC5 updates. A timeframe is about a fortnight till month from now.
*** Bug 191705 has been marked as a duplicate of this bug. ***
*** Bug 193879 has been marked as a duplicate of this bug. ***