Re: qemu-riscv32 usermode still broken?

Hi Alistair, > > Ok! > > So on my x86 machine I see this > > --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=285545, > si_uid=1000, si_status=0, si_utime=0, si_stime=0} --- > wait4(-1, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], > WNOHANG|WSTOPPED|WCONTINUED, NULL) = 285545 > wait4(-1,

Re: qemu-riscv32 usermode still broken?

Hi Alistair, > It would be great to get a strace of the failure to narrow down what > it is. From there it should be not too hard to find and fix. thanks a lot. Here's as much info as I could get with strace mechanisms. 1) What I did, without any tracing pinacolada ~ # qemu-riscv32 -L /var/lib

Re: qemu-riscv32 usermode still broken?

Am Donnerstag, 14. September 2023, 03:22:49 CEST schrieb Andreas K. Huettel: > > > https://lists.gnu.org/archive/html/bug-bash/2023-09/msg00119.html > > > ^ Here I'm trying to find out more. > > > > > > Bash tests apparently indicate that argv[0] is over

Re: qemu-riscv32 usermode still broken?

> > https://lists.gnu.org/archive/html/bug-bash/2023-09/msg00119.html > > ^ Here I'm trying to find out more. > > > > Bash tests apparently indicate that argv[0] is overwritten, and that > > reading through a pipe or from /dev/tty fails or loses data. > > > > Apart from the bash testsuite failing,

Re: qemu-riscv32 usermode still broken?

Am Mittwoch, 13. September 2023, 10:06:01 CEST schrieb Michael Tokarev: > 13.09.2023 04:41, LIU Zhiwei wrote: > > > > On 2023/9/13 6:31, Andreas K. Huettel wrote: > .. > >> * Something seems wrong in the signal handling (?): > > > > If it is wrong for sig

qemu-riscv32 usermode still broken?

Dear all, I've once more tried to build up a riscv32 linux install in a qemu-riscv32 usermode systemd-nspawn, and am running into the same problems as some time ago... https://dev.gentoo.org/~dilfridge/riscv32/riscv32.tar.xz (220M) The problems manifest themselves mostly in bash; if I replace

Re: [PATCH RESEND] linux-user: Fix struct statfs ABI on loongarch64

inux-user: Add LoongArch syscall support") > Signed-off-by: WANG Xuerui > Cc: Song Gao > Cc: Xiaojuan Yang > Cc: Andreas K. Hüttel > --- > > Resend with amended commit message to 100% clarify the example output > are generated on my box and will differ for everyone els

Re: [PATCH] linux-user: Fix more MIPS n32 syscall ABI issues

at the (host and qemu) strace outputs, and > would have to ask you to review/test this harder. Thanks. This solves the problem I observed in https://gitlab.com/qemu-project/qemu/-/issues/1238 Thank you!! Tested by having one mipsel n32 chroot rebuild itself completely. Tested-by: Andr

Re: [PATCH] target/mips: Fix address space range declaration on n32

> Closes: https://gitlab.com/qemu-project/qemu/-/issues/939 > Signed-off-by: WANG Xuerui > Cc: Philippe Mathieu-Daudé > Cc: Aurelien Jarno > Cc: Jiaxun Yang > Cc: Aleksandar Rikalo > Cc: Andreas K. Hüttel > --- Tested-by: Andreas K. Huettel > target/mips/cpu-

Re: [PATCH] linux-user/signal: Map exit signals in SIGCHLD siginfo_t

Am Sonntag, 19. Dezember 2021, 00:32:09 CET schrieb Matthias Schiffer: > On 23/10/2021 21:59, Matthias Schiffer wrote: > > When converting a siginfo_t from waitid(), the interpretation of si_status > > depends on the value of si_code: For CLD_EXITED, it is an exit code and > > should be copied verb

Re: [PATCH] linux-user/signal: Map exit signals in SIGCHLD siginfo_t

Well, the original fix 1c3dfb506ea3 did clearly improve things for me, but it wasn't complete yet. At some point I gave up on finding a minimal reproducer for my remaining problems (futex-related hangs in a complex python+bash app). So, this *may* be the missing piece. Will test, but that take