qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Launchpad Bug Tracker <2072564@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 2072564] Re: qemu-aarch64-static segfaults running ldconfig.real (amd64 host)
Date: Wed, 26 Feb 2025 09:46:52 -0000	[thread overview]
Message-ID: <174056321357.824404.10701750874521962485.launchpad@scripts-bzrsyncd.lp.internal> (raw)
In-Reply-To: 172053137048.3332067.13534832802726064667.malonedeb@juju-98d295-prod-launchpad-7

** Merge proposal linked:
   https://code.launchpad.net/~slyon/ubuntu/+source/qemu/+git/qemu/+merge/481940

** Merge proposal linked:
   https://code.launchpad.net/~slyon/ubuntu/+source/qemu/+git/qemu/+merge/481941

-- 
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:
  Fix Released
Status in qemu package in Ubuntu:
  Triaged
Status in qemu source package in Noble:
  Triaged
Status in qemu source package in Oracular:
  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



  parent reply	other threads:[~2025-02-26  9:56 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <172053137048.3332067.13534832802726064667.malonedeb@juju-98d295-prod-launchpad-7>
2024-07-11  2:03 ` [Bug 2072564] Re: qemu-aarch64-static segfaults running ldconfig.real (amd64 host) Sergio Durigan Junior
2024-07-11 21:19 ` Bug Watch Updater
2024-07-31 12:56 ` Michał Fita
2024-10-01 20:06 ` Sergio Durigan Junior
2024-10-23 14:26 ` Thomas Irgang
2025-01-06 11:05 ` Christian Ehrhardt 
2025-01-30 16:19 ` Sergio Durigan Junior
2025-02-19 12:34 ` Dimitry Andric
2025-02-19 12:59 ` Christian Ehrhardt
2025-02-19 18:14 ` Bug Watch Updater
2025-02-19 20:29 ` Ubuntu Foundations Team Bug Bot
2025-02-26  9:01 ` Launchpad Bug Tracker
2025-02-26  9:34 ` Christian Ehrhardt
2025-02-26  9:46 ` Launchpad Bug Tracker [this message]
2025-02-26  9:55 ` Launchpad Bug Tracker
2025-02-26 11:15 ` Lukas Märdian
2025-02-26 15:52 ` Lukas Märdian
2025-02-27 23:24 ` Launchpad Bug Tracker
2025-03-04 19:33 ` Michał Fita
2025-03-04 19:47 ` Dimitry Andric
2025-03-12 16:45 ` Lukas Märdian
2025-04-09 17:37 ` Andreas Hasenack
2025-04-09 17:40 ` [Bug 2072564] Please test proposed package Andreas Hasenack
2025-04-09 17:43 ` Andreas Hasenack
2025-04-10  1:26 ` [Bug 2072564] Autopkgtest regression report (qemu/1:9.0.2+ds-4ubuntu5.3) Ubuntu SRU Bot
2025-04-10  3:00 ` [Bug 2072564] Autopkgtest regression report (qemu/1:8.2.2+ds-0ubuntu1.7) Ubuntu SRU Bot
2025-04-10 10:45 ` [Bug 2072564] Re: qemu-aarch64-static segfaults running ldconfig.real (amd64 host) Dimitry Andric
2025-04-16  9:09 ` Lukas Märdian
2025-04-16  9:14 ` Lukas Märdian
2025-05-19 13:51 ` Launchpad Bug Tracker
2025-05-19 13:51 ` [Bug 2072564] Update Released Timo Aaltonen
2025-05-19 14:15 ` [Bug 2072564] Re: qemu-aarch64-static segfaults running ldconfig.real (amd64 host) Dimitry Andric
2025-05-19 14:25 ` Launchpad Bug Tracker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=174056321357.824404.10701750874521962485.launchpad@scripts-bzrsyncd.lp.internal \
    --to=2072564@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).