public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/65684] Wrong error message when writing to a string
Date: Wed, 08 Apr 2015 09:46:00 -0000	[thread overview]
Message-ID: <bug-65684-4-zLfaVwRSsT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65684-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65684

--- Comment #7 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> Fair enough... I have no experience in coding for GCC. Could you give me
> a hint where (which file) to start? 

The content of the message is set by 'translate_error (int code)' (line 412 of
libgfortran/runtime/error.c).

> I would propose a message like
>
> > At line 5 of file test.F90
> > Fortran runtime error: End of record (number of characters to be written
> > exceeds the length of the record)

I did not looked further to the code (you can grep for LIBERROR_EOR
libgfortran/runtime/* libgfortran/io/*, and gcc/fortran/* to find where it is
set) but I am not sure that "End of record" cannot be emitted when reading or
for unformatted files. If so your message will be misleading.


  parent reply	other threads:[~2015-04-08  9:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07 11:27 [Bug fortran/65684] New: " a.vogt at fulguritus dot com
2015-04-07 11:29 ` [Bug fortran/65684] " a.vogt at fulguritus dot com
2015-04-07 16:24 ` kargl at gcc dot gnu.org
2015-04-07 16:47 ` a.vogt at fulguritus dot com
2015-04-07 19:07 ` jvdelisle at gcc dot gnu.org
2015-04-08  9:02 ` dominiq at lps dot ens.fr
2015-04-08  9:23 ` a.vogt at fulguritus dot com
2015-04-08  9:46 ` dominiq at lps dot ens.fr [this message]
2015-04-08 10:21 ` a.vogt at fulguritus dot com
2015-04-08 18:38 ` a.vogt at fulguritus dot com
2015-04-09 12:24 ` jvdelisle at gcc dot gnu.org
2015-04-21 18:33 ` jvdelisle 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-65684-4-zLfaVwRSsT@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: 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).