On Tue, Jan 10, 2012 at 00:33, Tobias Burnus wrote:
> Dear Janne,
>
>
>> - The integer values for the signal numbers are not standardized,
>> hence printing them might give the user a false impression that these
>> numbers convey some information beyond whichever SIG* macro they map
>> to on that
Dear Janne,
- The integer values for the signal numbers are not standardized,
hence printing them might give the user a false impression that these
numbers convey some information beyond whichever SIG* macro they map
to on that particular target.
- It doesn't test all the signals which are actu
On Mon, Jan 9, 2012 at 21:21, Tobias Burnus wrote:
> Hello,
>
> in GCC 4.6, gfortran printed before the backtrace, e.g.,
> Program received signal 8 (SIGFPE): Floating-point exception.
> to STDERR followed by the backtrace.
>
> This was done by registering an error handler and - finishing with a
On Mon, Jan 09, 2012 at 08:21:31PM +0100, Tobias Burnus wrote:
>
> With the patch, one can get (cf. PR) an output to STDERR like:
>
> Program received signal 8 (SIGFPE): Floating-point exception.
>
> Backtrace for this error:
> #0 0x805891F in _gfortrani_show_backtrace at backtrace.c:261
> #1
Hello,
in GCC 4.6, gfortran printed before the backtrace, e.g.,
Program received signal 8 (SIGFPE): Floating-point exception.
to STDERR followed by the backtrace.
This was done by registering an error handler and - finishing with a
sys_exit(5). Since 4.7 with the patch for PR 48915 (comment 3
