Public bug reported:
Python's documentation search needs libjs-underscore to work.
The dependency is there for python3.4-doc, but not 2.7.
This is similar to bug #1001585 in which a symlink to underscore.js was
missing. Now the symlink is there, but its target is not except by
coincidence.
At l
Public bug reported:
Running the Samba autobuild tests on a 15.04 openstack image results in
a segfault in this command:
/usr/bin/xsltproc --nonet -o default/docs-xml/manpages/smb.conf.5
/home/ubuntu/autobuild/b22271/samba/docs-xml/xslt/man.xsl default/docs-
xml/manpages/smb.conf.5.xml
I reporte
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 o
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 U
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 0
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 t
It seems like a kernel thing. brk is returning bad addresses. Below,
tail is an unaffected process, and xsltproc is affected. brk should be
returning a 7 digit hex address, like it does for tail.
$ head -2 *.strace
==> tail.strace <==
execve("/usr/bin/tail", ["tail", "xsltproc.strace"], [/* 33 var
Bug is fixed in upstream kernel 4.2.0 rc3, with the heap getting roughly
800Mb to use and the stack 135.
80085000-8008a000 r-xp fd:01 58216 /usr/bin/xsltproc
8008a000-8008b000 r--p 4000 fd:01 58216 /usr/bin/xsltproc
8008b000-8008c000 rw-p 5000 fd:01 58216 /usr/bin/x
So, it isn't the ld-linux.so, it is the kernel on 32 bit i386, where
exec is loading PIE elf binaries in such a way that the heap and the
stack are next to each other and have very little room. About 20% of
/usr/bin/* (and others, like /bin/systemd) on the vivid cloud image is
affected, though in m
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1471029/+attachment/4432282/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxslt in Ubuntu.
https://b
apport information
** Tags added: apport-collected ec2-images vivid
** Description changed:
Running the Samba autobuild tests on a 15.04 openstack image results in
a segfault in this command:
/usr/bin/xsltproc --nonet -o default/docs-xml/manpages/smb.conf.5
/home/ubuntu/autobuild/b222
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1471029/+attachment/4432285/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxslt in Ubuntu.
https:/
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1471029/+attachment/4432286/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxslt in Ubuntu.
https://bugs.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1471029/+attachment/4432284/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxslt in Ubuntu.
https://bugs.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1471029/+attachment/4432287/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxslt in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1471029/+attachment/4432283/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxslt in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1471029/+attachment/4432288/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxslt in Ubuntu.
https://bugs.la
hi Joseph
Those packages don't want to install on the i386:
dpkg: error processing archive
linux-tools-3.16.0-44-generic_3.16.0-44.59~lp1471029_amd64.deb (--install):
package architecture (amd64) does not match system (i386)
(In compiling the 4.2 upstream kernel for i386, I ended up usi
Thanks Joseph!
It's no better with 3.16.0-44-generic #59~lp1471029. Perhaps even slightly
worse -- in my sample of 2 I've seen the heap at b8d- and b94-, while I think
stock Vivid 3.19 was most often in the b7's.
$ uname -a
Linux samba-build-i386-4-32bit 3.16.0-44-generic #59~lp1471029 SMP Wed
hi Colin,
I first met on a 3.19.0-20 build:
Linux samba-build-i386-32bit 3.19.0-20-generic #20-Ubuntu SMP Fri May 29
10:06:53 UTC 2015 i686 i686 i686 GNU/Linux
and as far as I can tell (taking into account Joseph's 3.16 and upstream
4.2rc3), that a87938b/b51621a commit is neither the cure or cul
> I'll try to find out what my VM actually is, beyond "openstack".
KVM 2.0.0+dfsg-2ubuntu1.11
The processor (per attached files above) is "Intel Xeon E312xx (Sandy
Bridge)".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to li
22 matches
Mail list logo