24.05.2014 Views

XL Fortran Enterprise Edition for AIX : User's Guide - IBM

XL Fortran Enterprise Edition for AIX : User's Guide - IBM

XL Fortran Enterprise Edition for AIX : User's Guide - IBM

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Other Environment Variables That Affect Run-Time Behavior<br />

The LIBPATH and TMPDIR environment variables have an effect at run time, as<br />

explained in “Correct Settings <strong>for</strong> Environment Variables” on page 12. They are not<br />

<strong>XL</strong> <strong>Fortran</strong> run-time options and cannot be set in either <strong>XL</strong>FRTEOPTS or<br />

<strong>XL</strong>SMPOPTS.<br />

<strong>XL</strong> <strong>Fortran</strong> Run-Time Exceptions<br />

The following operations cause run-time exceptions in the <strong>for</strong>m of SIGTRAP<br />

signals, which typically result in a “Trace/BPT trap” message:<br />

v Fixed-point division by zero.<br />

v Character substring expression or array subscript out of bounds after you<br />

specified the -C option at compile time.<br />

v Lengths of character pointer and target do not match after you specified the -C<br />

option at compile time.<br />

v The flow of control in the program reaches a location <strong>for</strong> which a semantic error<br />

with severity of S was issued when the program was compiled.<br />

v Floating-point exceptions occur after you specify the appropriate -qflttrap<br />

suboptions at compile time.<br />

v Floating-point operations that generate NaN values and loads of the NaN values<br />

after you specify the -qfloat=nanq option at compile time.<br />

If you install one of the predefined <strong>XL</strong> <strong>Fortran</strong> exception handlers be<strong>for</strong>e the<br />

exception occurs, a diagnostic message and a traceback showing the offset within<br />

each routine called that led to the exception are written to standard error after the<br />

exception occurs. The file buffers are also flushed be<strong>for</strong>e the program ends. If you<br />

compile the program with the -g option, the traceback shows source line numbers<br />

in addition to the address offsets.<br />

You can use a symbolic debugger to determine the error. dbx provides a specific<br />

error message that describes the cause of the exception.<br />

Related In<strong>for</strong>mation: See “-C Option” on page 103, “-qflttrap Option” on page<br />

165, and “-qsigtrap Option” on page 232.<br />

See “Detecting and Trapping Floating-Point Exceptions” on<br />

page 296 <strong>for</strong> more details about these exceptions and<br />

“Controlling the Floating-Point Status and Control Register”<br />

on page 299 <strong>for</strong> a list of exception handlers.<br />

66 <strong>XL</strong> <strong>Fortran</strong> <strong>Enterprise</strong> <strong>Edition</strong> <strong>for</strong> <strong>AIX</strong> : User’s <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!