public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jb at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/67414] [5/6 Regression] Error message on failed allocate
Date: Wed, 02 Sep 2015 14:52:00 -0000	[thread overview]
Message-ID: <bug-67414-4-88kZ1340Io@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67414-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Janne Blomqvist <jb at gcc dot gnu.org> ---
Author: jb
Date: Wed Sep  2 14:51:40 2015
New Revision: 227404

URL: https://gcc.gnu.org/viewcvs?rev=227404&root=gcc&view=rev
Log:
PR 67414 Better diagnostics on backtrace failure, gf_strerror bugfix

2015-09-02  Janne Blomqvist  <jb@gcc.gnu.org>

        PR libfortran/67414
        * io/write.c (gfc_itoa): Move to runtime/string.c.
        * libgfortran.h (show_backtrace): Make arg bool.
        (gfc_itoa): New prototype.
        * runtime/backtrace.c (struct mystate): Change type of try_simple
        field, add in_signal_handler field.
        (error_callback): Print out error number, or if not in a signal
        handler, the error message.
        (show_backtrace): Change type of arg, change initialization of
        struct mystate.
        (backtrace): Call show_backtrace with correct arg type.
        * runtime/compile_options.c (backtrace_handler): Call with correct
        arg type.
        * runtime/error.c (sys_abort): Likewise.
        (gf_strerror): Handle newlocale() failure.
        * runtime/string.c (gfc_itoa): Function moved here from
        io/write.c.

Modified:
    trunk/libgfortran/ChangeLog
    trunk/libgfortran/io/write.c
    trunk/libgfortran/libgfortran.h
    trunk/libgfortran/runtime/backtrace.c
    trunk/libgfortran/runtime/compile_options.c
    trunk/libgfortran/runtime/error.c
    trunk/libgfortran/runtime/string.c


  parent reply	other threads:[~2015-09-02 14:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31 16:32 [Bug fortran/67414] New: [5 " Joost.VandeVondele at mat dot ethz.ch
2015-08-31 21:03 ` [Bug fortran/67414] " jb at gcc dot gnu.org
2015-09-01  8:34 ` [Bug fortran/67414] [5/6 " rguenth at gcc dot gnu.org
2015-09-02 14:52 ` jb at gcc dot gnu.org [this message]
2015-09-02 15:16 ` jb 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-67414-4-88kZ1340Io@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).