Previous Next Contents Generated Index Doc Set Home



Error Handling

If the programmer calls a BLAS2 subroutine with an illegal argument value then the subroutine will call the error handling subroutine XERBLA. XERBLA will print the name of the subroutine, the number of the first argument found to be in error, and the values of the scalar arguments. The values of the arguments with the same types are printed together. As an example, consider the following call to DGBMV:

CALL DGBMV ('ILLEGAL', -1, 3, 1, 1, 2.0D0, A, LDA, X, 1, 3.0D0, Y, 1)

In the call above, the value of TRANSA is illegal. DGBMV will call XERBLA, which will print the report shown below and then terminate with a STOP statement.



 ** On entry to DGBMV  parameter number  1 had an illegal value
 
 CHARACTER PARAMETERS:
    I       
 
 INTEGER PARAMETERS:
         -1         3         1         1         3         1
          1
 
 REAL PARAMETERS:
     0.2000E+01    0.3000E+01


STOP

The Sun Performance Library will detect all instances in which the calling subprogram specifies one or more illegal argument values, but there are many types of interface errors that the Sun Performance Library will not detect. Included in the list of interface errors that the Sun Performance Library will not detect are too many or too few arguments, an argument of the wrong type, and an argument aliased with the result argument.




Previous Next Contents Generated Index Doc Set Home