public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jv244 at cam dot ac dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/40330] [4.4 Regression] incorrect IO
Date: Tue, 09 Jun 2009 22:15:00 -0000 [thread overview]
Message-ID: <20090609221459.2009.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40330-6642@http.gcc.gnu.org/bugzilla/>
------- Comment #15 from jv244 at cam dot ac dot uk 2009-06-09 22:14 -------
(In reply to comment #14)
> Closing as fixed.
I'm testing now 4.4 which includes your fix, but I still see CP2K's restarts
failing. This looks like a second issue, different from what you've fixed so
far. The testcase of comment #5 is working fine, with the update 4.4.1, but
CP2K runs still shows a valgrind warning:
==11664==
==11664== Invalid read of size 1
==11664== at 0x4BE3C4C: formatted_transfer (transfer.c:874)
==11664== by 0x6312C5: __input_section_types_MOD_section_vals_write
(input_section_types.F:2040)
==11664== by 0x632964: __input_section_types_MOD_section_vals_write
(input_section_types.F:2083)
==11664== by 0xF10D05: __replica_types_MOD_rep_env_create
(replica_types.F:278)
==11664== by 0x11996B9: __vibrational_analysis_MOD_vb_anal
(vibrational_analysis.F:143)
==11664== by 0x40E83A: __cp2k_runs_MOD_cp2k_run (cp2k_runs.F:385)
==11664== by 0x404E93: __cp2k_runs_MOD_run_input (cp2k_runs.F:1095)
==11664== by 0x403EBF: MAIN__ (cp2k.F:272)
==11664== by 0x2CFF029: main (fmain.c:21)
==11664== Address 0x6ada7c6 is 6 bytes inside a block of size 640 free'd
==11664== at 0x4A2196E: free (vg_replace_malloc.c:323)
==11664== by 0x631306: __input_section_types_MOD_section_vals_write
(input_section_types.F:2040)
==11664== by 0x632964: __input_section_types_MOD_section_vals_write
(input_section_types.F:2083)
==11664== by 0xF10D05: __replica_types_MOD_rep_env_create
(replica_types.F:278)
==11664== by 0x11996B9: __vibrational_analysis_MOD_vb_anal
(vibrational_analysis.F:143)
==11664== by 0x40E83A: __cp2k_runs_MOD_cp2k_run (cp2k_runs.F:385)
==11664== by 0x404E93: __cp2k_runs_MOD_run_input (cp2k_runs.F:1095)
==11664== by 0x403EBF: MAIN__ (cp2k.F:272)
==11664== by 0x2CFF029: main (fmain.c:21)
==11664==
==11664== Invalid read of size 1
==11664== at 0x4BE3C60: formatted_transfer (transfer.c:878)
==11664== by 0x6312C5: __input_section_types_MOD_section_vals_write
(input_section_types.F:2040)
==11664== by 0x632964: __input_section_types_MOD_section_vals_write
(input_section_types.F:2083)
==11664== by 0xF10D05: __replica_types_MOD_rep_env_create
(replica_types.F:278)
==11664== by 0x11996B9: __vibrational_analysis_MOD_vb_anal
(vibrational_analysis.F:143)
==11664== by 0x40E83A: __cp2k_runs_MOD_cp2k_run (cp2k_runs.F:385)
==11664== by 0x404E93: __cp2k_runs_MOD_run_input (cp2k_runs.F:1095)
==11664== by 0x403EBF: MAIN__ (cp2k.F:272)
==11664== by 0x2CFF029: main (fmain.c:21)
==11664== Address 0x6ada7c7 is 7 bytes inside a block of size 640 free'd
==11664== at 0x4A2196E: free (vg_replace_malloc.c:323)
==11664== by 0x631306: __input_section_types_MOD_section_vals_write
(input_section_types.F:2040)
==11664== by 0x632964: __input_section_types_MOD_section_vals_write
(input_section_types.F:2083)
==11664== by 0xF10D05: __replica_types_MOD_rep_env_create
(replica_types.F:278)
==11664== by 0x11996B9: __vibrational_analysis_MOD_vb_anal
(vibrational_analysis.F:143)
==11664== by 0x40E83A: __cp2k_runs_MOD_cp2k_run (cp2k_runs.F:385)
==11664== by 0x404E93: __cp2k_runs_MOD_run_input (cp2k_runs.F:1095)
==11664== by 0x403EBF: MAIN__ (cp2k.F:272)
==11664== by 0x2CFF029: main (fmain.c:21)
linking to the 4.3.2 runtime still solves the issue. I hope you can have a look
at what might be wrong with these traces above, I don't have a testcase other
than CP2K right now, and the code is tricky to reduce at that point.
If you happen to have CP2K around, this is the testcase for the trace:
cp2k/tests/Fist/regtest-5> valgrind --tool=memcheck
../../../exe/Linux-x86-64-gfortran/cp2k.sdbg wat_freq.inp
--
jv244 at cam dot ac dot uk changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |critical
Status|RESOLVED |REOPENED
Resolution|FIXED |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40330
next prev parent reply other threads:[~2009-06-09 22:15 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 15:45 [Bug libfortran/40330] New: " jv244 at cam dot ac dot uk
2009-06-03 15:46 ` [Bug libfortran/40330] " jv244 at cam dot ac dot uk
2009-06-03 15:54 ` dominiq at lps dot ens dot fr
2009-06-03 16:08 ` jv244 at cam dot ac dot uk
2009-06-03 16:32 ` jv244 at cam dot ac dot uk
2009-06-03 16:47 ` jv244 at cam dot ac dot uk
2009-06-03 16:49 ` jv244 at cam dot ac dot uk
2009-06-03 16:58 ` jv244 at cam dot ac dot uk
2009-06-03 17:39 ` jb at gcc dot gnu dot org
2009-06-03 18:49 ` jb at gcc dot gnu dot org
2009-06-03 19:19 ` jb at gcc dot gnu dot org
2009-06-03 21:07 ` jb at gcc dot gnu dot org
2009-06-04 5:16 ` jv244 at cam dot ac dot uk
2009-06-04 5:37 ` burnus at gcc dot gnu dot org
2009-06-09 20:56 ` jb at gcc dot gnu dot org
2009-06-09 20:58 ` jb at gcc dot gnu dot org
2009-06-09 22:15 ` jv244 at cam dot ac dot uk [this message]
2009-06-10 2:18 ` jvdelisle at gcc dot gnu dot org
2009-06-10 3:11 ` jvdelisle at gcc dot gnu dot org
2009-06-10 6:45 ` burnus at gcc dot gnu dot org
2009-06-10 7:22 ` [Bug libfortran/40330] [4.4, 4.5 " jv244 at cam dot ac dot uk
2009-06-10 7:24 ` jv244 at cam dot ac dot uk
2009-06-10 9:26 ` jv244 at cam dot ac dot uk
2009-06-10 12:32 ` jvdelisle at gcc dot gnu dot org
2009-06-10 13:18 ` jv244 at cam dot ac dot uk
2009-06-10 21:18 ` jb at gcc dot gnu dot org
2009-06-11 1:29 ` jvdelisle at gcc dot gnu dot org
2009-06-11 2:25 ` jvdelisle at gcc dot gnu dot org
2009-06-11 7:04 ` jv244 at cam dot ac dot uk
2009-06-11 12:50 ` jvdelisle at gcc dot gnu dot org
2009-06-11 14:58 ` [Bug libfortran/40330] [4.5 " jvdelisle at gcc dot gnu dot org
2009-06-12 5:48 ` jv244 at cam dot ac dot uk
2009-06-26 15:50 ` jvdelisle at gcc dot gnu dot org
2009-07-05 2:12 ` jvdelisle at gcc dot gnu dot org
2009-07-05 12:25 ` jvdelisle at gcc dot gnu dot org
2009-07-09 1:20 ` jvdelisle at gcc dot gnu dot org
2009-07-09 1:55 ` jvdelisle at gcc dot gnu dot org
2009-07-09 1:59 ` jvdelisle at gcc dot gnu dot org
2009-07-12 14:49 ` jv244 at cam dot ac dot uk
2009-07-23 17:52 ` hjl 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=20090609221459.2009.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: link
Be 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).