Bug#1040981: klibc-utils: segfault executing armhf binaries under qemu-user

2023-07-13 Thread Helge Deller
On 7/14/23 01:56, Thorsten Glaser wrote: Dixi quod… My guess here is that it’s, as usual, the fault of qemu-user, Strong evidence for that: doesn’t look like it even executes one bit of klibc code: $ qemu-arm-static -d cpu ./fstype --help qemu: uncaught target signal 11 (Segmentation fault)

Bug#1040981: klibc-utils: segfault executing armhf binaries under qemu-user

2023-07-13 Thread Thorsten Glaser
Dixi quod… >My guess here is that it’s, as usual, the fault of qemu-user, Strong evidence for that: doesn’t look like it even executes one bit of klibc code: $ qemu-arm-static -d cpu ./fstype --help qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentation fault (core

Bug#1040981: klibc-utils: segfault executing armhf binaries under qemu-user

2023-07-13 Thread Thorsten Glaser
Hi Helge, >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) I doubt it, klibc malloc uses mmap(2) normally. (And given I tested it on a bullseye system, the

Bug#1040981: klibc-utils: segfault executing armhf binaries under qemu-user

2023-07-13 Thread Thorsten Glaser
Dixi quod… >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*