Sun Performance Library Reference Manual: 1

Error Handling

If the programmer calls a LAPACK subroutine with an illegal argument value then the subroutine will call the error handling subroutine XERBLA. XERBLA will print the name of the subroutine in which the error was detected and the number of the first argument found to be in error. As an example, consider the following call to DGBCON:


CALL DGBCON ('ILLEGAL', -526, SUB, SUPER, A, LDA, IPIV,ANORM, RC, WRK, IWRK, INFO)

In the call above, the values of NORM and N (the first two arguments) are illegal. DGBCON will call XERBLA, which will print the report shown below and then terminate with a STOP statement.

** On entry to DGBCON parameter number 1 had an illegal value

STOP

** On entry to DGBCON parameter number 1 had an illegal value STOP

The Sun Performance Library will detect all instances in which the calling subprogram specifies one or more illegal parameter 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 is specifying too many or too few arguments, specifying an argument of the wrong type, and aliasing an argument with the result argument.