From: Xi Ruoyao <xry111@xry111.site>
To: gcc@gcc.gnu.org
Cc: Lulu Cheng <chenglulu@loongson.cn>, Wang Xuerui <i@xen0n.name>,
Chenghua Xu <xuchenghua@loongson.cn>
Subject: Re: "random" segment faults in expect running GCC regression test on LoongArch
Date: Thu, 17 Nov 2022 22:15:37 +0800 [thread overview]
Message-ID: <8900ac3f1ea2e9bf5e5dff21734ea5f8f284e761.camel@xry111.site> (raw)
In-Reply-To: <2e88c9803e5b57aa3f320c9722dcb700b6a47420.camel@xry111.site>
On Wed, 2022-11-09 at 15:43 +0800, Xi Ruoyao wrote:
> Hi,
>
> This is a "help wanted" message. When I run GCC regression test on
> loongarch64-linux-gnu, expect occasionally crashes with a segment fault.
> The stack backtrace is like:
/* snip */
> The crashes happen on both my own LoongArch board and
> gcc401.fsffrance.org. So I don't think it was an "only me" problem.
>
> The segment fault is not deterministic. A Expect command like
>
> cd /path/to/gcc/build/gcc
> expect -- /usr/share/dejagnu/runtest.exp --tool gfortran dg.exp=bind-c-contiguous-1.f90
>
> sometimes succeeds, sometimes immediately segfaults, sometimes prints
> several lines of strange error message and then exits abnormally.
>
> Usually I don't like to send "help wanted" messages, but this time I
> have no idea how to fix (or even triage) the problem. I don't even know
> which component (Tcl? Expect? GCC? Glibc? Kernel?) I should blame. So
> it seems I really need some help now...
I'm now 99% sure this is a kernel issue:
https://lore.kernel.org/loongarch/20221117042532.4064448-1-chenhuacai@loongson.cn/
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
prev parent reply other threads:[~2022-11-17 14:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 7:43 Xi Ruoyao
2022-11-17 14:15 ` Xi Ruoyao [this message]
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=8900ac3f1ea2e9bf5e5dff21734ea5f8f284e761.camel@xry111.site \
--to=xry111@xry111.site \
--cc=chenglulu@loongson.cn \
--cc=gcc@gcc.gnu.org \
--cc=i@xen0n.name \
--cc=xuchenghua@loongson.cn \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).