SIGSEGV in xsltproc

Dear OpenSuSE community,

After upgrading few libraries (which does not look to be relevant to xsltproc), xsltproc started to SIGSEGV:

# /usr/bin/xsltproc manual.sgml
Segmentation fault

# strace /usr/bin/xsltproc manual.sgml
execve("/usr/bin/xsltproc", "/usr/bin/xsltproc", "manual.sgml"], /* 67 vars */]) = 0
brk(0)                                  = 0x804f000
... cut ...
stat64("/usr/share/xml/docbook/schema/dtd/4.5/dbnotnx.mod", {st_mode=S_IFREG|0644, st_size=4521, ...}) = 0
stat64("/usr/share/xml/docbook/schema/dtd/4.5/dbnotnx.mod", {st_mode=S_IFREG|0644, st_size=4521, ...}) = 0
stat64("/usr/share/xml/docbook/schema/dtd/4.5/dbnotnx.mod", {st_mode=S_IFREG|0644, st_size=4521, ...}) = 0
open("/usr/share/xml/docbook/schema/dtd/4.5/dbnotnx.mod", O_RDONLY|O_LARGEFILE) = 5
_llseek(5, 0, [0], SEEK_CUR)            = 0
read(5, "<!-- ..........................."..., 8192) = 4521
read(5, "", 3671)                       = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
Segmentation fault

Are there any ideas, where to look at?

Additional info:

# ldd /usr/bin/xsltproc | /usr/bin/egrep -i -o '(/usr)?/lib/[A-Z\.0-9]+' | while read lib
; do ls -l1 $lib; done
lrwxrwxrwx 1 root root 17 Apr  1 14:21 /usr/lib/libxslt.so.1 -> libxslt.so.1.1.26
lrwxrwxrwx 1 root root 18 Apr  1 14:21 /usr/lib/libexslt.so.0 -> libexslt.so.0.8.15
lrwxrwxrwx 1 root root 16 Jun  1  2010 /usr/lib/libxml2.so.2 -> libxml2.so.2.7.3
lrwxrwxrwx 1 root root 14 Mar 29 16:33 /lib/libc.so.6 -> libc-2.11.3.so
lrwxrwxrwx 1 root root 14 Mar 29 16:33 /lib/libm.so.6 -> libm-2.11.3.so
lrwxrwxrwx 1 root root 19 May 31  2010 /lib/libgcrypt.so.11 -> libgcrypt.so.11.4.4
lrwxrwxrwx 1 root root 15 Mar 29 16:33 /lib/libdl.so.2 -> libdl-2.11.3.so
lrwxrwxrwx 1 root root 13 Mar 29 16:33 /lib/libz.so.1 -> libz.so.1.2.5

Sorry for report. I’ve decided to trace the problem with gdb. So I’ve installed gdb, which required the update of Python libraries:

zypper install gdb python python-sip python-base python-xml libxml2-python

After this xsltproc started to work normally. Either it get scared, or the installation procedure has triggered some updates… Dunno.

Closed.