This is a dynamic linking/loading problem, not related to libxml2 (or
xsltproc) as first thought. The problem seems to be that executables
with R_386_RELATIVE components are being mapped entirely (including the
heap) into memory between roughly B700 and BFFF, which gives
them roughly 140M
I tried some more things:
1. Compiling with clang makes no difference.
2. Compiling with -fsanitize=address results a stack overflow message
followed by a stack trace. It doesn't reveal as much as the post-mortum
traceback in gdb. The address sanitizer seems to make the error
deterministic.
3.
OK, so sampling the last two lines of the process map every 0.2 seconds:
start:
b772c000-b772e000 rw-p 5000 fd:01 67267 /usr/bin/xsltproc
bfe83000-bfea4000 rw-p 00:00 0 [stack]
0.2s
b7894000-b849e000 rw-p 00:00 0 [heap]
bfe83000-bfea4000 rw-p
Rebuilding libxml2_2.9.2+dfsg1-3_i386.deb from ubuntu source with -O0
fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1471029
Title:
Segfault in xsltproc
Actually I was wrong, -O0 doesn't fix it. Sorry.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1471029
Title:
Segfault in xsltproc on i386
Status in libxml2 package in
5 matches
Mail list logo
