From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"open list:RISC-V" <qemu-riscv@nongnu.org>
Cc: LIU Zhiwei <baxiantai@gmail.com>
Subject: Re: qemu-riscv32 usermode still broken?
Date: Thu, 14 Sep 2023 03:22:49 +0200 [thread overview]
Message-ID: <4344798.atdPhlSkOF@pinacolada> (raw)
In-Reply-To: <15820654-5d7f-fd66-3d34-da1a55d2a53e@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1494 bytes --]
> > 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, symptoms are as follows:
> >
> > * 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
>
> https://www.mail-archive.com/qemu-devel@nongnu.org/msg981238.html
>
> And this patch has been merged into master branch yesterday.
>
> May be you can have a try based on the master branch.
I added the patch to 8.0.3 (easier for the moment), and this did
unfortunately *not* lead to any improvements.
More debugging coming (weekend hopefully).
However, in the meantime on the GNU Make tracker Alejandro Colomar
pointed me to another detail based on my oddities [1]:
> I think [make] it's failing here:
>
> <https://git.savannah.gnu.org/cgit/make.git/tree/src/job.c#n757>
>
> But it's failing with ENOENT, which is not one of the documented
> errors for wait(2):
So maybe another point to look at would be the origin of the return
values of wait, and whether that's wired correctly for rv32...
[1] https://savannah.gnu.org/bugs/?64664
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next prev parent reply other threads:[~2023-09-14 1:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 22:31 qemu-riscv32 usermode still broken? Andreas K. Huettel
2023-09-13 1:41 ` LIU Zhiwei
2023-09-13 8:06 ` Michael Tokarev
2023-09-13 10:33 ` Andreas K. Huettel
2023-09-14 1:22 ` Andreas K. Huettel [this message]
2023-09-16 22:37 ` Andreas K. Huettel
2023-09-18 1:16 ` Alistair Francis
2023-09-19 20:39 ` Andreas K. Huettel
2024-06-11 4:43 ` Alistair Francis
2024-06-11 8:57 ` Andreas K. Huettel
2024-06-12 1:26 ` Alistair Francis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4344798.atdPhlSkOF@pinacolada \
--to=dilfridge@gentoo.org \
--cc=baxiantai@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.