public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/96041] [11 regression] ICE in gfortran.dg/pr93423.f90 after r11-1792
Date: Fri, 03 Jul 2020 18:27:01 +0000 [thread overview]
Message-ID: <bug-96041-4-JQxPeP3HOC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96041-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96041
--- Comment #1 from anlauf at gcc dot gnu.org ---
(In reply to Bill Seurer from comment #0)
> f951: internal compiler error: Segmentation fault
> 0x10be671b crash_signal
> /home/seurer/gcc/git/gcc-test/gcc/toplev.c:328
> 0x103a6484 free_st_labels
> /home/seurer/gcc/git/gcc-test/gcc/fortran/symbol.c:2662
> 0x103a648f free_st_labels
> /home/seurer/gcc/git/gcc-test/gcc/fortran/symbol.c:2662
> 0x103a648f free_st_labels
> /home/seurer/gcc/git/gcc-test/gcc/fortran/symbol.c:2662
> 0x103afd63 gfc_free_namespace(gfc_namespace*)
> /home/seurer/gcc/git/gcc-test/gcc/fortran/symbol.c:4044
Bill,
can you set a breakpoint at symbol.c:4044 and print ns->st_labels?
On x86_64 I always have a NULL pointer here, so that symbol.c:2662
is never reached.
next prev parent reply other threads:[~2020-07-03 18:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 22:45 [Bug fortran/96041] New: " seurer at linux dot vnet.ibm.com
2020-07-03 6:59 ` [Bug fortran/96041] " rguenth at gcc dot gnu.org
2020-07-03 18:27 ` anlauf at gcc dot gnu.org [this message]
2020-07-04 5:59 ` dominiq at lps dot ens.fr
2020-07-04 14:29 ` dominiq at lps dot ens.fr
2020-07-04 17:17 ` anlauf at gcc dot gnu.org
2020-07-06 14:35 ` seurer at linux dot vnet.ibm.com
2020-07-06 18:26 ` anlauf at gcc dot gnu.org
2020-07-07 12:03 ` dominiq at lps dot ens.fr
2020-07-07 19:31 ` anlauf at gcc dot gnu.org
2020-09-14 22:52 ` burnus at gcc dot gnu.org
2020-09-17 12:01 ` cvs-commit at gcc dot gnu.org
2020-09-17 12:07 ` burnus at gcc dot gnu.org
2020-09-18 20:19 ` cvs-commit at gcc dot gnu.org
2020-09-19 18:32 ` cvs-commit at gcc dot gnu.org
2020-09-19 18:42 ` cvs-commit at gcc dot gnu.org
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=bug-96041-4-JQxPeP3HOC@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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 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).