The previous patch was slightly over-zealous. Committed the following fix:
Index: gfortran.texi
===================================================================
--- gfortran.texi (revision 173769)
+++ gfortran.texi (working copy)
@@ -2611,7 +2611,7 @@ standard error. Default: @code{GFC_STD_
Default: off.
@item @var{option}[3] @tab Unused.
@item @var{option}[4] @tab If non zero, enable backtracing on run-time
-errors. Default: enabled.
+errors. Default: off.
Note: Installs a signal handler and requires command-line
initialization using @code{_gfortran_set_args}.
@item @var{option}[5] @tab If non zero, supports signed zeros.
Index: ChangeLog
===================================================================
--- ChangeLog (revision 173769)
+++ ChangeLog (working copy)
@@ -1,3 +1,9 @@
+2011-05-15 Janne Blomqvist <j...@gcc.gnu.org>
+
+ PR libfortran/48915
+ * gfortran.texi (_gfortran_set_options): Even though -fbacktrace
+ is now the default, the library defaults to backtracing disabled.
+
2011-05-14 Tobias Burnus <bur...@net-b.de>
* lang.opt (fdump-core): Re-add as ignored option
On Sat, May 14, 2011 at 13:24, Janne Blomqvist
<blomqvist.ja...@gmail.com> wrote:
> Hi,
>
> I committed the attached patch as obvious. It updates the manual
> section on mixed-language programming to reflect the changes made as
> part of PR 48915.
>
> Index: gfortran.texi
> ===================================================================
> --- gfortran.texi (revision 173750)
> +++ gfortran.texi (working copy)
> @@ -2578,7 +2578,7 @@ int main (int argc, char *argv[])
> @table @asis
> @item @emph{Description}:
> @code{_gfortran_set_options} sets several flags related to the Fortran
> -standard to be used, whether backtracing or core dumps should be enabled
> +standard to be used, whether backtracing should be enabled
> and whether range checks should be performed. The syntax allows for
> upward compatibility since the number of passed flags is specified; for
> non-passed flags, the default value is used. See also
> @@ -2609,10 +2609,9 @@ Possible values are (bitwise or-ed) @cod
> standard error. Default: @code{GFC_STD_F95_DEL | GFC_STD_LEGACY}.
> @item @var{option}[2] @tab If non zero, enable pedantic checking.
> Default: off.
> -@item @var{option}[3] @tab If non zero, enable core dumps on run-time
> -errors. Default: off.
> +@item @var{option}[3] @tab Unused.
> @item @var{option}[4] @tab If non zero, enable backtracing on run-time
> -errors. Default: off.
> +errors. Default: enabled.
> Note: Installs a signal handler and requires command-line
> initialization using @code{_gfortran_set_args}.
> @item @var{option}[5] @tab If non zero, supports signed zeros.
> @@ -2627,8 +2626,8 @@ Default: enabled. See -frange-check (@p
>
> @item @emph{Example}:
> @smallexample
> - /* Use gfortran 4.5 default options. */
> - static int options[] = @{68, 255, 0, 0, 0, 1, 0, 1@};
> + /* Use gfortran 4.7 default options. */
> + static int options[] = @{68, 255, 0, 0, 1, 1, 0, 1@};
> _gfortran_set_options (8, &options);
> @end smallexample
> @end table
> Index: ChangeLog
> ===================================================================
> --- ChangeLog (revision 173750)
> +++ ChangeLog (working copy)
> @@ -1,5 +1,12 @@
> 2011-05-14 Janne Blomqvist <j...@gcc.gnu.org>
>
> + PR libfortran/48915
> + * gfortran.texi: Update mixed-language programming section
> + reflecting the removal of the fdump-core option, and that
> + -fbacktrace is enabled by default.
> +
> +2011-05-14 Janne Blomqvist <j...@gcc.gnu.org>
> +
> PR libfortran/48915
> * gfortran.h (gfc_option_t): Remove flag_dump_core.
> * gfortran.texi (GFORTRAN_ERROR_DUMPCORE): Remove section.
>
>
> --
> Janne Blomqvist
>
--
Janne Blomqvist
