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 B7000000 and BFFFFFFF, which gives them roughly 140M to work with. Most programs can cope with that, but some (e.g. xsltproc performing described task) cannot.
I don't know whether to blame ld-linux.so or the kernel. This is on a 15.04 cloud image with 4GB running on openstack.
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 B7000000 and BFFFFFFF, which gives them roughly 140M to work with. Most programs can cope with that, but some (e.g. xsltproc performing described task) cannot.
I don't know whether to blame ld-linux.so or the kernel. This is on a 15.04 cloud image with 4GB running on openstack.