semantic: 0.887 graphic: 0.882 instruction: 0.881 device: 0.862 socket: 0.847 assembly: 0.822 network: 0.812 KVM: 0.798 other: 0.794 boot: 0.779 vnc: 0.718 mistranslation: 0.696 automoc4 segfaults when building in an armhf pbuilder on an amd64 host When trying to build kde4libs in an armhf pbuilder created with the pbuilder-scripts running on an amd64 host automoc4 recieves a segmentation fault and I can't get any useful information out of it: root@yofel-thinkpad:/tmp/kde4libs-4.9.3/build/kdeui# /usr/bin/automoc4 kdeui_automoc.cpp ../../kdeui/ . moc-qt4 cmake unable to dump 00102c00 Segmentation fault (core dumped) root@yofel-thinkpad:/tmp/kde4libs-4.9.3/build/kdeui# gdb /usr/bin/automoc4 qemu_automoc4_20121108-211818_15839.core GNU gdb (GDB) 7.5-ubuntu Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "arm-linux-gnueabihf". For bug reporting instructions, please see: ... Reading symbols from /usr/bin/automoc4...done. BFD: Warning: /tmp/kde4libs-4.9.3/build/kdeui/qemu_automoc4_20121108-211818_15839.core is truncated: expected core file size >= 5150720, found: 974848. [New LWP 15839] [New LWP 15866] Cannot access memory at address 0xf67fe954 Cannot access memory at address 0xf67fe950 (gdb) bt #0 0xf6630306 in ?? () #1 0xf6415ff8 in ?? () #2 0xf6415ff8 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) (gdb) automoc4 runs fine when building on a nexus7 so this sounds like an issue in qemu. Tested in quantal and raring. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: qemu-user-static 1.2.0-2012.09-0ubuntu1 Uname: Linux 3.6.2-030602-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.2-0ubuntu3 Architecture: amd64 Date: Fri Nov 9 19:29:28 2012 EcryptfsInUse: Yes InstallationDate: Installed on 2011-10-08 (398 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20111007) MarkForUpload: True ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 LANGUAGE=en_US.UTF-8 SourcePackage: qemu-linaro UpgradeStatus: No upgrade log present (probably fresh install) This still applies to raring's qemu with the linaro patches. Thanks for reporting this bug. There seem to be a few bugs in the armhf qemu-user-static right now. I'll test against bleeding edge upstream. Buildlog from an armfh PPA build as reference. Same for me make[2]: Entering directory `/builddir/build/BUILD/kdelibs-4.10.5/build' cd /builddir/build/BUILD/kdelibs-4.10.5/build/kdeui && /usr/bin/automoc4 /builddir/build/BUILD/kdelibs-4.10.5/build/kdeui/kdeui_automoc.cpp /builddir/build/BUILD/kdelibs-4.10.5/kdeui /builddir/build/BUILD/kdelibs-4.10.5/build/kdeui /usr/lib/qt4/bin/moc /usr/bin/cmake Unable to load library icui18n "Cannot load library icui18n: (icui18n: cannot open shared object file: No such file or directory)" qemu: uncaught target signal 11 (Segmentation fault) - core dumped /bin/sh: line 1: 8056 Segmentation fault (core dumped) /usr/bin/automoc4 /builddir/build/BUILD/kdelibs-4.10.5/build/kdeui/kdeui_automoc.cpp /builddir/build/BUILD/kdelibs-4.10.5/kdeui /builddir/build/BUILD/kdelibs-4.10.5/build/kdeui /usr/lib/qt4/bin/moc /usr/bin/cmake make[2]: *** [kdeui/CMakeFiles/kdeui_automoc] Error 139 make[2]: Leaving directory `/builddir/build/BUILD/kdelibs-4.10.5/build' make[1]: *** [kdeui/CMakeFiles/kdeui_automoc.dir/all] Error 2 make[1]: Leaving directory `/builddir/build/BUILD/kdelibs-4.10.5/build' make: *** [all] Error 2 make: Leaving directory `/builddir/build/BUILD/kdelibs-4.10.5/build' error: Bad exit status from /var/tmp/rpm-tmp.50015 (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.50015 (%install) I was able to reproduce this failure with QEMU 2.5, and the code runs OK under QEMU current master, so I think this is fixed by the threading/signal handling bugfixes we've done between then and now. I'm going to close this as will-be-fixed-in-2.11 (though it's quite possible it's already fixed in 2.10). We have had a few more issues around armhf qemu-static that mostly resolved in Artful (qemu 2.10) and finally one that was good in Bionic (qemu 2.11). This also included some updates to other components but should be good now. If the issue here really still applies to a newer version please reopen and state an updated test and version that it ran on.