It probably isn't useful, but the backtrace without extra debug symbols looks like this:
buildd@dogfood-lgw01-amd64-001:/build/xen-jT2uET/xen-4.16.0/xen/arch/x86$ gdb --args x86_64-linux-gnu-ld -mi386pep --subsystem=10 --image-base=0xffff82d040000000 --stack=0,0 --heap=0,0 --section-alignment=0x200000 --file-alignment=0x20 --major-image-version=4 --minor-image-version=16 --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp --build-id=sha1 -T efi.lds -N prelink.o /build/xen-jT2uET/xen-4.16.0/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o /build/xen-jT2uET/xen-4.16.0/xen/.xen.efi.0xffff82d040000000.0 GNU gdb (Ubuntu 11.2-0ubuntu1) 11.2 Copyright (C) 2022 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 x86_64-linux-gnu-ld... (No debugging symbols found in x86_64-linux-gnu-ld) (gdb) r Starting program: /usr/bin/x86_64-linux-gnu-ld -mi386pep --subsystem=10 --image-base=0xffff82d040000000 --stack=0,0 --heap=0,0 --section-alignment=0x200000 --file-alignment=0x20 --major-image-version=4 --minor-image-version=16 --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp --build-id=sha1 -T efi.lds -N prelink.o /build/xen-jT2uET/xen-4.16.0/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o /build/xen-jT2uET/xen-4.16.0/xen/.xen.efi.0xffff82d040000000.0 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Program received signal SIGSEGV, Segmentation fault. 0x00007ffff7ca3b4a in ?? () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x00007ffff7ca3b4a in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007ffff7f672d0 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #2 0x00007ffff7f2d1e8 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #3 0x00007ffff7f2d509 in coff_write_alien_symbol () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #4 0x00007ffff7f2e3bd in _bfd_coff_final_link () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #5 0x000055555559d3bf in ?? () #6 0x00007ffff7c13fd0 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x00007ffff7c1407d in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #8 0x000055555559c515 in ?? () -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958389 Title: Jammy builds of xen segfault, but only on launchpad x86 builders To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1958389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
