public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "spop at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/45117] New: Segfault in resolve_array_bound Date: Wed, 28 Jul 2010 20:49:00 -0000 [thread overview] Message-ID: <bug-45117-7780@http.gcc.gnu.org/bugzilla/> (raw) GCC segfaults on this program while printing diagnostic: SUBROUTINE DFTAX8A(F,H,MAPAUX,IAUXTYP,LOCAUX) COMMON /INFOA / NAT,ICH,MUL,NUM,NQMT,NE,NA,NB, * TMPTMP(NUM+NAUXFUN,NUM+NAUXFUN) END This happens in resolve_array_bound, on trying to access a NULL pointer: gfc_error ("Variable '%s' at %L in this context must be constant", e->symtree->n.sym->name, &e->where); (gdb) p e->symtree $26 = (gfc_symtree *) 0x0 -- Summary: Segfault in resolve_array_bound Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: spop at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45117
next reply other threads:[~2010-07-28 20:49 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-28 20:49 spop at gcc dot gnu dot org [this message] 2010-07-29 6:34 ` [Bug fortran/45117] [4.3/4.4/4.5/4.6 Regression] " burnus at gcc dot gnu dot org 2010-07-29 9:07 ` domob at gcc dot gnu dot org 2010-07-29 10:03 ` domob 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=bug-45117-7780@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).