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 libfortran/29649] Force core dump on runtime library errors Date: Thu, 18 Jan 2007 12:54:00 -0000 [thread overview] Message-ID: <20070118125428.19905.qmail@sourceware.org> (raw) In-Reply-To: <bug-29649-9410@http.gcc.gnu.org/bugzilla/> ------- Comment #14 from burnus at gcc dot gnu dot org 2007-01-18 12:54 ------- Subject: Bug 29649 Author: burnus Date: Thu Jan 18 12:54:11 2007 New Revision: 120897 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=120897 Log: 2007-01-18 Francois-Xavier Coudert <coudert@clipper.ens.fr> Tobias Burnus <burnus@net-b.de> PR libfortran/29649 * gfortran.h (gfc_option_t): Add flag_dump_core. * lang.opt: Add -fdump-core option. * invoke.texi: Document the new options. * trans-decl.c (gfc_build_builtin_function_decls): Add new options to the call to set_std. * options.c (gfc_init_options, gfc_handle_option): Set the new options. 2007-01-18 Francois-Xavier Coudert <coudert@clipper.ens.fr> Tobias Burnus <burnus@net-b.de> PR libfortran/29649 * runtime/environ.c (variable_table): New GFORTRAN_ERROR_DUMPCORE environment variable. * runtime/compile_options.c (set_std): Add new argument. * runtime/error.c (sys_exit): Move from io/unix.c. Add coredump functionality. * libgfortran.h (options_t): New dump_core and backtrace members. (sys_exit): Move prototype. * io/unix.c (sys_exit): Move to runtime/error.c. * configure.ac: Add check for getrlimit. * configure: Regenerate. Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/gfortran.h trunk/gcc/fortran/invoke.texi trunk/gcc/fortran/lang.opt trunk/gcc/fortran/options.c trunk/gcc/fortran/trans-decl.c trunk/libgfortran/ChangeLog trunk/libgfortran/configure trunk/libgfortran/configure.ac trunk/libgfortran/io/unix.c trunk/libgfortran/libgfortran.h trunk/libgfortran/runtime/compile_options.c trunk/libgfortran/runtime/environ.c trunk/libgfortran/runtime/error.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29649
next prev parent reply other threads:[~2007-01-18 12:54 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-10-30 12:21 [Bug fortran/29649] New: " sfilippone at uniroma2 dot it 2006-10-30 12:24 ` [Bug libfortran/29649] " fxcoudert at gcc dot gnu dot org 2006-10-30 12:30 ` P dot Schaffnit at access dot rwth-aachen dot de 2006-10-31 15:54 ` burnus at gcc dot gnu dot org 2006-10-31 16:01 ` fxcoudert at gcc dot gnu dot org 2006-10-31 16:03 ` fxcoudert at gcc dot gnu dot org 2006-10-31 18:37 ` burnus at gcc dot gnu dot org 2006-10-31 19:10 ` Andrew Pinski 2006-10-31 19:10 ` pinskia at physics dot uc dot edu 2006-11-02 23:42 ` pinskia at gcc dot gnu dot org 2006-11-02 23:52 ` fxcoudert at gcc dot gnu dot org 2006-11-19 14:58 ` fxcoudert at gcc dot gnu dot org 2007-01-02 14:30 ` fxcoudert at gcc dot gnu dot org 2007-01-02 15:10 ` burnus at gcc dot gnu dot org 2007-01-05 14:03 ` fxcoudert at gcc dot gnu dot org 2007-01-05 21:25 ` patchapp at dberlin dot org 2007-01-12 6:48 ` fxcoudert at gcc dot gnu dot org 2007-01-18 12:54 ` burnus at gcc dot gnu dot org [this message] 2007-01-18 12:56 ` 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=20070118125428.19905.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).