public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/32884] ICE: Accessing non-local variable in PURE function Date: Tue, 24 Jul 2007 18:29:00 -0000 [thread overview] Message-ID: <20070724182851.25034.qmail@sourceware.org> (raw) In-Reply-To: <bug-32884-13404@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from burnus at gcc dot gnu dot org 2007-07-24 18:28 ------- Others cannot reproduce it (on i686 & x86_64), but here I can with gfortran-4.1 & 4.2 of SUSE, with the vanilla 4.2 and with 4.3. The problem is for whatever reason the "&code->expr->where" argument to gfc_error(). In error_print the "loc" argument is not NULL, but loc->lb->* point to invalid locations, which gave an memory access error (segfault) in show_locus when accessing lb->file. 484 loc = va_arg (argp, locus *); 486 if (have_l1) (gdb) p loc $8 = (locus *) 0xfdc13a (gdb) p loc->lb $9 = (gfc_linebuf *) 0x610072616200736e (gdb) p loc->lb->file Cannot access memory at address 0x6100726162007376 (gdb) p loc->lb->line Cannot access memory at address 0x610072616200738a (gdb) p loc->lb->file Cannot access memory at address 0x6100726162007376 But no problem for others. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32884
next prev parent reply other threads:[~2007-07-24 18:29 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-07-24 17:19 [Bug fortran/32884] New: " burnus at gcc dot gnu dot org 2007-07-24 17:33 ` [Bug fortran/32884] " burnus at gcc dot gnu dot org 2007-07-24 18:29 ` burnus at gcc dot gnu dot org [this message] 2007-07-24 18:53 ` 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=20070724182851.25034.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).