Re: [gfortran,patch, RFC] Allow coredump and backtrace on runtime error

[Craig Powers <enigma at hal-pc dot org>]

Tobias Burnus wrote:
>  Counter example
> ifort (with trace enabled by default):
>
> forrtl: No such file or directory
> forrtl: severe (29): file not found, unit 77, file /dev/shm/not-existing.dat
> Image              PC                Routine            Line        Source
> a.out              00000000004394E6  Unknown               Unknown  Unknown
> a.out              000000000043809E  Unknown               Unknown  Unknown
> a.out              00000000004214F0  Unknown               Unknown  Unknown
> a.out              0000000000416602  Unknown               Unknown  Unknown
> a.out              0000000000416263  Unknown               Unknown  Unknown
> a.out              0000000000405F3B  Unknown               Unknown  Unknown
> a.out              00000000004026F5  Unknown               Unknown  Unknown
> a.out              000000000040266A  Unknown               Unknown  Unknown
> libc.so.6          00002B41F8C90AE4  Unknown               Unknown  Unknown
> a.out              00000000004025A9  Unknown               Unknown  Unknown
>
> Here it takes much longer until one has realized what went wrong. The
> only thing which is better is that the file name is given.

In my experience, ifort will always produce a trace, but only give 
useable routine/line/source info if you specify a flag, I think 
-traceback.  But I haven't combed through the options to see if there's 
something to turn off the automatic trace.