This may or may not be relevant here, but the mysterious "uncaught target signal 11" error was fixed for maas images (lp:maas-images) build process by increasing the memory to the VMs that were doing the build. We had been doing the cross/qemu-static building in ~512M vms and that was resulting in somewhat transient failures during 'apt-get update'. Upping the memory of the vm to 2G made those go away.
-- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1357226 Title: qemu: uncaught target signal 11 (Segmentation fault) - core dumped Status in QEMU: New Bug description: steps to reproduce: pbuilder-dist utopic armhf create pbuilder-dist utopic armhf login apt-get install imagemagick convert foo.xpm foo.png qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentation fault (doesn't matter if images are actually there or not) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1357226/+subscriptions
