From: Ian Lance Taylor <iant@golang.org>
To: Martin Sebor <msebor@gmail.com>
Cc: gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: gcc/testsuite/go/index0-out.x spinning
Date: Sun, 22 Sep 2019 01:29:00 -0000 [thread overview]
Message-ID: <CAOyqgcUT+XdtOiFDiCg6QwnTYvi_8SaRdv5Yzp013KSmgKnRBQ@mail.gmail.com> (raw)
In-Reply-To: <e12099bd-dd75-a722-fea3-96a07410e7ce@gmail.com>
On Sat, Sep 21, 2019 at 4:43 PM Martin Sebor <msebor@gmail.com> wrote:
>
> On 9/21/19 2:34 PM, Martin Sebor wrote:
> > On 9/19/19 10:56 PM, Ian Lance Taylor wrote:
> >> On Thu, Sep 19, 2019 at 7:10 PM Martin Sebor <msebor@gmail.com> wrote:
> >>>
> >>> All my Fedora 30 builds on x86_64 today have gotten stuck on
> >>> index0-out.x spinning indefinitely. I build and test all
> >>> languages, including Go, so I'm wondering if anyone else who
> >>> builds Go sees the same thing or if you know of a workaround.
> >>
> >> For what it's worth, I don't see this on Debian rodete at GCC SVN
> >> revision 275986.
> >
> > My build with the top of today's trunk also completed so it must
> > have been something transient. Still strange.
>
> Looks like I spoke too soon. It's hanging/spinning again. Do you
> have any suggestion for how I can help debug it?
Send the spinning process a SIGQUIT. It should crash with a stack
backtrace showing what it is doing at that point.
Ian
next prev parent reply other threads:[~2019-09-22 1:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 2:10 Martin Sebor
2019-09-20 4:56 ` Ian Lance Taylor
2019-09-21 20:34 ` Martin Sebor
2019-09-21 23:43 ` Martin Sebor
2019-09-22 1:29 ` Ian Lance Taylor [this message]
2019-09-23 6:18 Uros Bizjak
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=CAOyqgcUT+XdtOiFDiCg6QwnTYvi_8SaRdv5Yzp013KSmgKnRBQ@mail.gmail.com \
--to=iant@golang.org \
--cc=gcc@gcc.gnu.org \
--cc=msebor@gmail.com \
/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).