From: Uros Bizjak <ubizjak@gmail.com>
To: GCC Development <gcc@gcc.gnu.org>
Cc: Ian Taylor <iant@golang.org>, Martin Sebor <msebor@gmail.com>
Subject: Re: gcc/testsuite/go/index0-out.x spinning
Date: Mon, 23 Sep 2019 06:18:00 -0000 [thread overview]
Message-ID: <CAFULd4bK-ovnFdYfKgWoRneN6+6hRa=wdeQtw+0PuqusiC89pA@mail.gmail.com> (raw)
>> 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.
I see a segfault in seemingly a random place, even with ulimit -s
unlimited, mostly in:
Program received signal SIGSEGV, Segmentation fault.
__generic_morestack (pframe_size=0x2aaaaefd9cc0,
old_stack=0x2aaaaefd9ce0, param_size=0) at
../../../git/gcc/libgcc/generic-morestack.c:558
558 current->old_stack = old_stack;
(gdb) bt
#0 __generic_morestack (pframe_size=0x2aaaaefd9cc0,
old_stack=0x2aaaaefd9ce0, param_size=0) at
../../../git/gcc/libgcc/generic-morestack.c:558
#1 0x00002aaaabae4fb8 in __morestack () at
../../../git/gcc/libgcc/config/i386/morestack.S:512
#2 0x00002aaaabadd1f8 in backtrace_get_view
(state=state@entry=0x2aaaafb7e000, descriptor=descriptor@entry=2,
offset=offset@entry=1760592,
size=585728, error_callback=error_callback@entry=0x2aaaab557450
<error_callback>, data=data@entry=0x2aaaaefda6a0, view=0x2aaaaefd9fc0)
at ../../../git/gcc/libbacktrace/mmapio.c:79
#3 0x00002aaaabadc660 in elf_add (state=state@entry=0x2aaaafb7e000,
filename=filename@entry=0x7fffffffd8fc
"/home/uros/gcc-build/gcc/testsuite/go/index0-out.x",
descriptor=descriptor@entry=5,
base_address=base_address@entry=0,
error_callback=error_callback@entry=0x2aaaab557450 <error_callback>,
data=data@entry=0x2aaaaefda6a0,
fileline_fn=0x2aaaaefda238, found_sym=0x2aaaaefda230,
found_dwarf=0x2aaaaefda234, fileline_entry=0x0, exe=1, debuginfo=0,
with_buildid_data=0x0, with_buildid_size=0) at
../../../git/gcc/libbacktrace/elf.c:3158
#4 0x00002aaaabadd041 in backtrace_initialize
(state=state@entry=0x2aaaafb7e000,
filename=filename@entry=0x7fffffffd8fc
"/home/uros/gcc-build/gcc/testsuite/go/index0-out.x", descriptor=5,
error_callback=error_callback@entry=0x2aaaab557450
<error_callback>, data=data@entry=0x2aaaaefda6a0,
fileline_fn=fileline_fn@entry=0x2aaaaefda2d8) at
../../../git/gcc/libbacktrace/elf.c:3390
but sometimes in:
Program received signal SIGSEGV, Segmentation fault.
merge_dynamic_blocks (b=0x2, a=0x24) at
../../../git/gcc/libgcc/generic-morestack.c:420
420 for (pp = &a->next; *pp != NULL; pp = &(*pp)->next)
(gdb) bt
#0 merge_dynamic_blocks (b=0x2, a=0x24) at
../../../git/gcc/libgcc/generic-morestack.c:420
#1 __morestack_release_segments (free_dynamic=<optimized out>,
pp=<optimized out>) at ../../../git/gcc/libgcc/generic-morestack.c:455
#2 __generic_morestack (pframe_size=0x2aaaaefda150,
old_stack=0x2aaaaefda170, param_size=0) at
../../../git/gcc/libgcc/generic-morestack.c:546
#3 0x00002aaaabae4fb8 in __morestack () at
../../../git/gcc/libgcc/config/i386/morestack.S:512
#4 0x00002aaaabad75c1 in dwarf_lookup_pc
(state=state@entry=0x2aaaafb7e000, ddata=ddata@entry=0x2aaab18e5a18,
pc=<optimized out>,
pc@entry=46912507311387, callback=callback@entry=0x2aaaab5570c0 <callback>,
error_callback=error_callback@entry=0x2aaaab557450
<error_callback>, data=data@entry=0x2aaaaefda6a0, found=<optimized
out>)
at ../../../git/gcc/libbacktrace/dwarf.c:3021
Uros.
next reply other threads:[~2019-09-23 6:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 6:18 Uros Bizjak [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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='CAFULd4bK-ovnFdYfKgWoRneN6+6hRa=wdeQtw+0PuqusiC89pA@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=iant@golang.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).