public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dfranke at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/37829] ICE in resolve_symbol Date: Fri, 28 Nov 2008 21:25:00 -0000 [thread overview] Message-ID: <20081128212344.13834.qmail@sourceware.org> (raw) In-Reply-To: <bug-37829-87@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from dfranke at gcc dot gnu dot org 2008-11-28 21:23 ------- Confirmed. $> gfortran-svn gcc version 4.4.0 20081128 (experimental) (GCC) (gdb) run pr37829.f90 Starting program: /home/daniel/i686-pc-linux-gnu/gcc/libexec/gcc/i686-pc-linux-gnu/4.4.0/f951 pr37829.f90 Program received signal SIGSEGV, Segmentation fault. resolve_symbol (sym=0x9f57f58) at /home/daniel/svn/gcc-svn/gcc/fortran/resolve.c:9229 9229 if (sym->ts.type == BT_DERIVED (gdb) bt #0 resolve_symbol (sym=0x9f57f58) at /home/daniel/svn/gcc-svn/gcc/fortran/resolve.c:9229 #1 0x080c737e in traverse_ns (st=0x9f57f38, func=0x80b9880 <resolve_symbol>) at /home/daniel/svn/gcc-svn/gcc/fortran/symbol.c:3126 #2 0x080c736a in traverse_ns (st=0x9f585a0, func=0x80b9880 <resolve_symbol>) at /home/daniel/svn/gcc-svn/gcc/fortran/symbol.c:3123 #3 0x080c736a in traverse_ns (st=0x9f5cdc0, func=0x80b9880 <resolve_symbol>) at /home/daniel/svn/gcc-svn/gcc/fortran/symbol.c:3123 #4 0x080b59b2 in resolve_types (ns=<value optimized out>) at /home/daniel/svn/gcc-svn/gcc/fortran/resolve.c:10346 #5 0x080b985c in gfc_resolve (ns=0x9f5c4b0) at /home/daniel/svn/gcc-svn/gcc/fortran/resolve.c:10427 #6 0x080a6fbf in gfc_parse_file () at /home/daniel/svn/gcc-svn/gcc/fortran/parse.c:3844 #7 0x080d721d in gfc_be_parse_file (set_yydebug=0) at /home/daniel/svn/gcc-svn/gcc/fortran/f95-lang.c:236 #8 0x08391e7c in toplev_main (argc=2, argv=0xbfcef534) at /home/daniel/svn/gcc-svn/gcc/toplev.c:968 #9 0xb7e20005 in __libc_start_main () from /lib/libc.so.6 -- dfranke at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dfranke at gcc dot gnu dot | |org Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Known to fail| |4.3.2 4.4.0 Last reconfirmed|0000-00-00 00:00:00 |2008-11-28 21:23:44 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37829
next prev parent reply other threads:[~2008-11-28 21:25 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-10-14 20:09 [Bug fortran/37829] New: " jakub at gcc dot gnu dot org 2008-11-28 21:25 ` dfranke at gcc dot gnu dot org [this message] 2008-12-08 21:07 ` [Bug fortran/37829] " mikael at gcc dot gnu dot org 2008-12-09 8:43 ` dominiq at lps dot ens dot fr 2008-12-09 13:54 ` mikael at gcc dot gnu dot org 2008-12-09 17:30 ` burnus at gcc dot gnu dot org 2008-12-15 12:50 ` dominiq at lps dot ens dot fr 2009-10-23 15:02 ` dominiq at lps dot ens dot fr 2009-10-24 22:42 ` mikael at gcc dot gnu dot org 2009-10-25 15:34 ` dominiq at lps dot ens dot fr 2009-12-06 15:40 ` [Bug fortran/37829] ICE Incorrect name mangling with iso_c_binding jvdelisle at gcc dot gnu dot org 2010-07-09 8:39 ` [Bug fortran/37829] " burnus at gcc dot gnu dot org 2010-07-09 8:48 ` burnus at gcc dot gnu dot org 2010-08-05 17:51 ` mikael at gcc dot gnu dot org 2010-08-14 9:31 ` burnus at gcc dot gnu dot org 2010-08-14 16:24 ` burnus at gcc dot gnu dot 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=20081128212344.13834.qmail@sourceware.org \ --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: linkBe 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).