qemu-aarch64-static segfaults
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
QEMU |
Fix Released
|
Undecided
|
Unassigned | ||
qemu (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
I've found a couple conditions that causes qemu-user-static to core dump fairly reliably - same with upstream git - while a binary built from suse's aarch64-1.6 branch seems to consistently work fine.
Testing suggests they are resolved by the sigprocmask wrapper patches included in suse's tree.
1) dh_fixperms is a script that commonly runs at the end of a package build.
Its basically doing a `find | xargs chmod`.
2) debootstrap --second-stage
This is used to configure an arm64 chroot that was built using
debootstrap on a non-native host. It is basically invoking a bunch of
shell scripts (postinst, etc). When it blows up, the stack consistently
looks like this:
Core was generated by `/usr/bin/
/debootstrap/
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x0000000060058e55 in memcpy (__len=8, __src=0x7fff62a
__dest=
/usr/include/
51 return __builtin_
(gdb) bt
#0 0x0000000060058e55 in memcpy (__len=8, __src=0x7fff62a
__dest=
/usr/include/
#1 stq_p (v=274886476624, ptr=0x400082c330) at
/mnt/qemu.
#2 stq_le_p (v=274886476624, ptr=0x400082c330) at
/mnt/qemu.
#3 target_
sf=0x400082b0d0) at /mnt/qemu.
#4 target_setup_frame (usig=usig@
<sigact_table+512>, info=info@
env=env@
at /mnt/qemu.
#5 0x0000000060059f46 in setup_frame (env=0x62d9c678,
set=0x7fff62ae3530, ka=0x604ec1e0 <sigact_table+512>, sig=17) at
/mnt/qemu.
#6 process_
/mnt/qemu.
#7 0x0000000060056e60 in cpu_loop (env=env@
/mnt/qemu.
#8 0x0000000060005079 in main (argc=<optimized out>, argv=<optimized
out>, envp=<optimized out>) at
/mnt/qemu.
Related branches
Changed in qemu (Ubuntu): | |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in qemu: | |
status: | Fix Committed → Fix Released |
The attachment "qemu.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]