[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1129571] Re: libreoffice armhf FTBFS
From: |
Serge Hallyn |
Subject: |
[Qemu-devel] [Bug 1129571] Re: libreoffice armhf FTBFS |
Date: |
Wed, 20 Feb 2013 18:32:47 -0000 |
address@hidden:~$ /usr/lib/jvm/default-java/bin/javac --version
#
# A fatal error has been detected by the Java Runtime Environment:
#
# Internal Error (os_linux_zero.cpp:285), pid=326, tid=4120921200
# fatal error: caught unhandled signal 11
#
# JRE version: 7.0_13-b20
# Java VM: OpenJDK Zero VM (22.0-b10 mixed mode linux-arm )
# Derivative: IcedTea7 2.3.6
# Distribution: Ubuntu Raring Ringtail (development branch), package
7u13-2.3.6-1ubuntu1
# Failed to write core dump. Core dumps have been disabled. To enable core
dumping, try
"ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/ubuntu/hs_err_pid326.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
# https://bugs.launchpad.net/ubuntu/+source/openjdk-7/
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
qemu: uncaught target signal 6 (Aborted) - core dumped
Aborted (core dumped)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1129571
Title:
libreoffice armhf FTBFS
Status in QEMU:
New
Status in “qemu” package in Ubuntu:
Confirmed
Bug description:
We have been experiencing FTBFS of LibreOffice 3.5.7, 12.04, armhf in
the launchpad buildds. We believe this is likely due to an error in
qemu.
While we do not have a small test case yet, we do have a build log
(attaching here).
The relevant snippet from the build log is:
3.5.7/solver/unxlngr.pro/bin/jaxp.jar:/build/buildd/libreoffice-3.5.7/solver/unxlngr.pro/bin/juh.jar:/build/buildd/libreoffice-3.5.7/solver/unxlngr.pro/bin/parser.jar:/build/buildd/libreoffice-3.5.7/solver/unxlngr.pro/bin/xt.jar:/build/buildd/libreoffice-3.5.7/solver/unxlngr.pro/bin/unoil.jar:/build/buildd/libreoffice-3.5.7/solver/unxlngr.pro/bin/ridl.jar:/build/buildd/libreoffice-3.5.7/solver/unxlngr.pro/bin/jurt.jar:/build/buildd/libreoffice-3.5.7/solver/unxlngr.pro/bin/xmlsearch.jar:/build/buildd/libreoffice-3.5.7/solver/unxlngr.pro/bin/LuceneHelpWrapper.jar:/build/buildd/libreoffice-3.5.7/solver/unxlngr.pro/bin/HelpIndexerTool.jar:/build/buildd/libreoffice-3.5.7/solver/unxlngr.pro/bin/lucene-core-2.3.jar:/build/buildd/libreoffice-3.5.7/solver/unxlngr.pro/bin/lucene-analyzers-2.3.jar"
com.sun.star.help.HelpIndexerTool -lang cs -mod swriter -zipdir
../../unxlngr.pro/misc/ziptmpswriter_cs -o
../../unxlngr.pro/bin/swriter_cs.zip.unxlngr.pro
dmake: Error code 132, while making '../../unxlngr.pro/bin/swriter_cs.zip'
We believe this is from bash error code 128 + 4, where 4 is illegal
instruction, thus leading us to suspect qemu.
Any help in tracking this down would be appreciated.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1129571/+subscriptions