Bug#1040981: klibc-utils: Segmentation fault while executin klibc binaries in armhf architecture under qemu-user
Can you check if this patch fixes the problem: https://patchew.org/QEMU/mvmpm55qnno@suse.de/ (linux-user: make sure brk(0) returns a page-aligned value, from Andreas Schwab) Ursprüngliche Nachricht Von: Thorsten Glaser Datum: 14.07.23 00:48 (GMT+01:00) An: venkata.p...@toshiba-tsip.com, 1040...@bugs.debian.org, pkg-qemu-de...@lists.alioth.debian.org Cc: dinesh.ku...@toshiba-tsip.com Betreff: Bug#1040981: klibc-utils: Segmentation fault while executin klibc binaries in armhf architecture under qemu-user retitle 1040981 klibc-utils: segfault executing armhf binaries under qemu-userthanksvenkata.p...@toshiba-tsip.com dixit:>Follow below steps to reproduce this issue>```>$ sudo debootstrap --arch=arm bookworm arm-bookworm-rootfs/ http://deb.debian.org/debian/>$ sudo chroot arm-bookworm/ apt-update && apt install -y klibc-utils>$ sudo chroot arm-bookworm/ /usr/lib/klibc/bin/fstype --help>qemu: uncaught target signal 11 (Segmentation fault) - core dumped>Segmentation fault>```Same when just copying klibc-m13AniKHUCMUNN8mXSUhIi8CUSA.so outof libklibc_2.0.12-1_armhf.deb into /lib/ and extracting fstypefrom klibc-utils_2.0.12-1_armhf.deb… however it works both on areal-metal ARM box (amdahl.d.o) and a statically(!) linked mkshagainst klibc :/My guess here is that it’s, as usual, the fault of qemu-user,which has multiple outstanding emulation bugs, some of whichaffecting klibc-built binaries especially, though this, sincea statically linked mksh works, is probably an issue with howqemu-user handles .interp *shrug*Since your one-stage debootstrap succeeds, can you not do theremaining steps booting into the image-under-preparation andrun them there? Here, qemu-system-armhf should probably suffice.I know, it’s just as a workaround, until the people in questionfigure out why this happens.bye,//mirabilos-- Solange man keine schmutzigen Tricks macht, und ich meine *wirklich*schmutzige Tricks, wie bei einer doppelt verketteten Liste beidePointer XORen und in nur einem Word speichern, funktioniert Boehm ganzhervorragend. -- Andreas Bogk über boehm-gc in d.a.s.r
Processed: Re: Bug#1040981: klibc-utils: Segmentation fault while executin klibc binaries in armhf architecture under qemu-user
Processing commands for cont...@bugs.debian.org: > retitle 1040981 klibc-utils: segfault executing armhf binaries under qemu-user Bug #1040981 [klibc-utils] klibc-utils: Segmentation fault while executin klibc binaries in armhf architecture Changed Bug title to 'klibc-utils: segfault executing armhf binaries under qemu-user' from 'klibc-utils: Segmentation fault while executin klibc binaries in armhf architecture'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1040981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040981 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040981: klibc-utils: Segmentation fault while executin klibc binaries in armhf architecture under qemu-user
retitle 1040981 klibc-utils: segfault executing armhf binaries under qemu-user thanks venkata.p...@toshiba-tsip.com dixit: >Follow below steps to reproduce this issue >``` >$ sudo debootstrap --arch=arm bookworm arm-bookworm-rootfs/ >http://deb.debian.org/debian/ >$ sudo chroot arm-bookworm/ apt-update && apt install -y klibc-utils >$ sudo chroot arm-bookworm/ /usr/lib/klibc/bin/fstype --help >qemu: uncaught target signal 11 (Segmentation fault) - core dumped >Segmentation fault >``` Same when just copying klibc-m13AniKHUCMUNN8mXSUhIi8CUSA.so out of libklibc_2.0.12-1_armhf.deb into /lib/ and extracting fstype from klibc-utils_2.0.12-1_armhf.deb… however it works both on a real-metal ARM box (amdahl.d.o) and a statically(!) linked mksh against klibc :/ My guess here is that it’s, as usual, the fault of qemu-user, which has multiple outstanding emulation bugs, some of which affecting klibc-built binaries especially, though this, since a statically linked mksh works, is probably an issue with how qemu-user handles .interp *shrug* Since your one-stage debootstrap succeeds, can you not do the remaining steps booting into the image-under-preparation and run them there? Here, qemu-system-armhf should probably suffice. I know, it’s just as a workaround, until the people in question figure out why this happens. bye, //mirabilos -- Solange man keine schmutzigen Tricks macht, und ich meine *wirklich* schmutzige Tricks, wie bei einer doppelt verketteten Liste beide Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz hervorragend. -- Andreas Bogk über boehm-gc in d.a.s.r
