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/36276] [4.3/4.4 Regression] possible issue with opening fortran files? Date: Sat, 14 Jun 2008 17:00:00 -0000 [thread overview] Message-ID: <20080614170016.27850.qmail@sourceware.org> (raw) In-Reply-To: <bug-36276-6642@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from burnus at gcc dot gnu dot org 2008-06-14 17:00 ------- For completeness, the line was added by r128676 | fxcoudert | 2007-09-23 01:48:02 +0200 (So, 23. Sep 2007) | 5 lines PR fortran/33528 The invalid read happens for linemap_add's "to_file". Above the function there is the note: The text pointed to by TO_FILE must have a lifetime at least as long as the final call to lookup_line (). My feeling is that current_file->filename is freed too early. FX, do you have an idea? -- burnus at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fxcoudert at gcc dot gnu dot | |org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36276
next prev parent reply other threads:[~2008-06-14 17:00 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-05-20 10:16 [Bug fortran/36276] New: " jv244 at cam dot ac dot uk 2008-05-20 10:17 ` [Bug fortran/36276] " jv244 at cam dot ac dot uk 2008-05-20 15:29 ` jv244 at cam dot ac dot uk 2008-05-22 20:00 ` [Bug fortran/36276] [4.3/4.4 Regression] " pinskia at gcc dot gnu dot org 2008-05-28 22:10 ` rguenth at gcc dot gnu dot org 2008-05-29 12:41 ` burnus at gcc dot gnu dot org 2008-06-06 15:04 ` rguenth at gcc dot gnu dot org 2008-06-14 16:48 ` burnus at gcc dot gnu dot org 2008-06-14 17:00 ` burnus at gcc dot gnu dot org [this message] 2008-06-16 17:55 ` burnus at gcc dot gnu dot org 2008-06-20 13:58 ` lauras at gcc dot gnu dot org 2008-06-21 10:03 ` [Bug fortran/36276] [4.3 " burnus at gcc dot gnu dot org 2008-06-21 15:31 ` lauras at gcc dot gnu dot org 2008-06-21 21:40 ` lauras 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=20080614170016.27850.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).