Re: qemu-riscv32 usermode still broken?

2024-06-11 Thread Alistair Francis
On Tue, Jun 11, 2024 at 6:57 PM Andreas K. Huettel wrote: > > 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) &&

Re: qemu-riscv32 usermode still broken?

2024-06-11 Thread Andreas K. Huettel
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?

2024-06-10 Thread Alistair Francis
On Wed, Sep 20, 2023 at 6:39 AM Andreas K. Huettel wrote: > > 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. > >

Re: qemu-riscv32 usermode still broken?

2023-09-19 Thread Andreas K. Huettel
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

Re: qemu-riscv32 usermode still broken?

2023-09-17 Thread Alistair Francis
On Sun, Sep 17, 2023 at 8:38 AM Andreas K. Huettel wrote: > > 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

Re: qemu-riscv32 usermode still broken?

2023-09-16 Thread Andreas K. Huettel
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 overwritten, and that > > > reading through a

Re: qemu-riscv32 usermode still broken?

2023-09-13 Thread 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 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?

2023-09-13 Thread Andreas K. Huettel
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 signal handling and for 32-bit, I guess it

Re: qemu-riscv32 usermode still broken?

2023-09-13 Thread 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 signal handling and for 32-bit, I guess it may be fixed by this patch

Re: qemu-riscv32 usermode still broken?

2023-09-12 Thread LIU Zhiwei
On 2023/9/13 6:31, Andreas K. Huettel wrote: 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

qemu-riscv32 usermode still broken?

2023-09-12 Thread Andreas K. Huettel
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