www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rainer Jung (JIRA)" <j...@apache.org>
Subject [jira] [Created] (INFRA-6357) xsltproc crash on people.a.o after FreeBSD 9.1 upgrade
Date Thu, 06 Jun 2013 14:23:21 GMT
Rainer Jung created INFRA-6357:

             Summary: xsltproc crash on people.a.o after FreeBSD 9.1 upgrade
                 Key: INFRA-6357
                 URL: https://issues.apache.org/jira/browse/INFRA-6357
             Project: Infrastructure
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: Other/Misc
         Environment: people.apache.org FreeBSD 9.1, libxml2 2.8.0 and libxslt 1.1.28 from
            Reporter: Rainer Jung

apsite build jobs crash xsltproc after upgrade of FreeBSD to 9.1 on people.apache.org.

I was able to strip this down to a simple test case which directly runs xsltproc.

gdb shows we are always crashing in

#0  0x00000008036ba21b in pthread_mutex_lock () from /lib/libthr.so.3
#1  0x000000080139c635 in xmlRMutexLock () from /usr/local/lib/libxml2.so.5
#2  0x0000000801397a6c in xmlCatalogCleanup () from /usr/local/lib/libxml2.so.5
#3  0x000000080133353a in xmlCleanupParser () from /usr/local/lib/libxml2.so.5

This happens at the end of the xsltproc run, when all the work is already done, but xmlCleanupParser
is called.

The same test case shows no problem on eos running FreeBSD 9.0.

It seems to be a threading and/or build issue. The libxml2 ports contains a patch to configure,
that effectively removed -D_REENTRANT for FreeBSD from CPFLAGS. This patch is reported to
be problematic for other users as well. Beware that the same patch was already part of FreeBSD
9.0, but there the version of libxml2 was 2.7.8, not 2.8.0.

I'm currently running out of time, so can't yet proceed to investigate.

Possible workaround: ignore crash in any script using xsltproc, because the actual processing
has finished at the time of crash (hoping output was not buffered).

Possible further investigations:

- check whether ports has a working libxml2 2.9.0
- build 2.8. without the configure patch for THREAD_CFLAGS

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message