[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug 2072564] Re: qemu-aarch64-static segfaults running ldconfig.real (a
From: |
Michał Fita |
Subject: |
[Bug 2072564] Re: qemu-aarch64-static segfaults running ldconfig.real (amd64 host) |
Date: |
Wed, 31 Jul 2024 12:56:24 -0000 |
I'm using quemu to tweak Armbian Jammy images for Raspberry Pi 5 (so it
would have ldconfig from 22.04) and I have signal 11 when libc
reconfiguration is triggered by apt.
What you may find interesting running the same process of updates on the
same base image on Ubuntu 22.04 (which has qemu 6.2) works fine.
My googling around "libc signal 11 quemu" lead to a lot of people
reporting problems with docker buildx with qemu predating 7.0. This
smells kind of regression in 8.2 used in 24.04. Then the issue linked
above says affected ldconfigs are 2.33 to 2.35...
Does Ubuntu really need to wait for upstream to deal with this? It's a
huge slap in the face for everyone on 24.04 needing to meddle 22.04
ARM64 images.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/2072564
Title:
qemu-aarch64-static segfaults running ldconfig.real (amd64 host)
Status in QEMU:
New
Status in qemu package in Ubuntu:
Triaged
Bug description:
This affects the qemu-user-static 1:8.2.2+ds-0ubuntu1 package on
Ubuntu 24.04, running on a amd64 host.
When running docker containers with Ubuntu 22.04 in them, emulating
arm64 with qemu-aarch64-static, invocations of ldconfig (actually
ldconfig.real) segfault. For example:
$ docker run -ti --platform linux/arm64/v8 ubuntu:22.04
root@8861ff640a1c:/# /sbin/ldconfig.real
Segmentation fault
If you copy the ldconfig.real binary to the host, and run it directly
via qemu-aarch64-static:
$ gdb --args qemu-aarch64-static ./ldconfig.real
GNU gdb (Ubuntu 15.0.50.20240403-0ubuntu1) 15.0.50.20240403-git
Copyright (C) 2024 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 "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from qemu-aarch64-static...
Reading symbols from
/home/dim/.cache/debuginfod_client/86579812b213be0964189499f62f176bea817bf2/debuginfo...
(gdb) r
Starting program: /usr/bin/qemu-aarch64-static ./ldconfig.real
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff76006c0 (LWP 28378)]
Thread 1 "qemu-aarch64-st" received signal SIGSEGV, Segmentation fault.
0x00007fffe801645b in ?? ()
(gdb) disassemble
No function contains program counter for selected frame.
It looks like this is a known qemu regression after v8.1.1:
https://gitlab.com/qemu-project/qemu/-/issues/1913
Downgrading the package to qemu-user-
static_8.0.4+dfsg-1ubuntu3_amd64.deb fixes the segfault.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/2072564/+subscriptions