[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1077116] Re: automoc4 segfaults when building in an ar
From: |
Serge Hallyn |
Subject: |
[Qemu-devel] [Bug 1077116] Re: automoc4 segfaults when building in an armhf pbuilder on an amd64 host |
Date: |
Wed, 20 Feb 2013 15:44:37 -0000 |
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.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1077116
Title:
automoc4 segfaults when building in an armhf pbuilder on an amd64 host
Status in QEMU:
New
Status in “qemu” package in Ubuntu:
Confirmed
Bug description:
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:
address@hidden:/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)
address@hidden:/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 <http://gnu.org/licenses/gpl.html>
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:
<http://www.gnu.org/software/gdb/bugs/>...
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)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1077116/+subscriptions