Prev: Temporary (hopefully) farewell to Usenet
Next: VMS LIB$
From: Jerry DeLisle on 23 Jun 2010 23:36
On 05/14/2010 07:31 PM, robert.corbett(a)oracle.com wrote:
> When Oracle Solaris Fortran terminates execution because of an
> end-of-file condition, it writes a message to standard error and then
> calls the C library routine abort. The C routine abort tries to close
> all open files and then raises SIGABRT. If there is no signal handler
> for SIGABRT, the OS will normally try to produce a core file.
>
> I recently received a request from a user asking that abort not be
> called for an end-of-file condition. He made the point that on
> modern machines core files are often gigabytes long and take
> some minutes to write.
>
> If a user does not want a core file to be produced, he can set the
> limit on the size of a core file to zero. That has the effect of
> suppressing production of a core file for any exception.
>
> I would like to know what others think of this request. Also, should
> abort be called for the end-of-record condition and i/o error
> conditions?
>
> Robert Corbett

Read the definitions of END=, EOR=, and ERR= , only ERR is really an error.

Short of a segmentation fault or someone actually calling abort, I don't think
the core dump you describe should happen at all.

Jerry
 | 
Pages: 1
Prev: Temporary (hopefully) farewell to Usenet
Next: VMS LIB$