public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zeccav at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/58813] New: SIGSEGV in show_locus at error.c:310 Date: Sun, 20 Oct 2013 07:27:00 -0000 [thread overview] Message-ID: <bug-58813-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58813 Bug ID: 58813 Summary: SIGSEGV in show_locus at error.c:310 Product: gcc Version: 4.8.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: zeccav at gmail dot com ! SIGSEGV in show_locus at error.c:310 ! must be compiled as free form ! if seen as fixed format no SIGSEGV ! valgrind and sanitizer say invalid read at symbol.c:5001 "dummies = sym->formal;" ! sym already freed at symbol.c:2519? In gfc_free_symbol "free (sym);" ! linked to bug 56674? MODULE m PUBLIC t CONTAINS SUBROUTINE s TYPE(t) END SUBROUTINE END MODULE !f951: internal compiler error: Segmentation fault !0x869b1f crash_signal ! ../../gcc-4.8.2/gcc/toplev.c:332 !0x50b1eb show_locus ! ../../gcc-4.8.2/gcc/fortran/error.c:310 !0x50ba80 show_loci ! ../../gcc-4.8.2/gcc/fortran/error.c:434 !0x50ba80 error_print ! ../../gcc-4.8.2/gcc/fortran/error.c:666 !0x50c568 gfc_error(char const*, ...) ! ../../gcc-4.8.2/gcc/fortran/error.c:961 !0x5142e7 check_interface0 ! ../../gcc-4.8.2/gcc/fortran/interface.c:1477 !0x516bc4 check_sym_interfaces ! ../../gcc-4.8.2/gcc/fortran/interface.c:1589 !0x57e493 do_traverse_symtree ! ../../gcc-4.8.2/gcc/fortran/symbol.c:3575 !0x516cac gfc_check_interfaces(gfc_namespace*) ! ../../gcc-4.8.2/gcc/fortran/interface.c:1699 !0x55d31e resolve_types ! ../../gcc-4.8.2/gcc/fortran/resolve.c:14989 !0x55dba0 gfc_resolve ! ../../gcc-4.8.2/gcc/fortran/resolve.c:15073 !0x552286 gfc_parse_file() ! ../../gcc-4.8.2/gcc/fortran/parse.c:4614 !0x58e195 gfc_be_parse_file ! ../../gcc-4.8.2/gcc/fortran/f95-lang.c:189 !Please submit a full bug report, !with preprocessed source if appropriate. !Please include the complete backtrace with any bug report.
next reply other threads:[~2013-10-20 7:27 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-10-20 7:27 zeccav at gmail dot com [this message] 2013-10-20 17:55 ` [Bug fortran/58813] " kargl at gcc dot gnu.org 2013-10-20 18:40 ` kargl at gcc dot gnu.org 2013-10-21 16:01 ` burnus at gcc dot gnu.org 2013-10-21 16:18 ` sgk at troutmask dot apl.washington.edu 2013-10-21 17:38 ` zeccav at gmail dot com 2013-10-22 13:08 ` sgk at troutmask dot apl.washington.edu 2013-10-22 17:14 ` zeccav at gmail dot com 2013-11-25 0:58 ` kargl at gcc dot gnu.org 2015-04-10 11:30 ` mikael at gcc dot gnu.org 2015-04-14 9:18 ` mikael at gcc dot gnu.org 2015-04-14 12:24 ` mikael at gcc dot gnu.org 2015-04-14 12:43 ` mikael 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-58813-4@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: 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).