
Error Bulletin for the NAG
C Library 
This document contains a list of errors that affect various
Marks of the NAG C Library.
Some of these errors may have been fixed at intermediate "point" releases of
the Library, while other fixes are scheduled for incorporation at future
releases. For library Marks where those fixes are not yet incorporated, a
workaround for the known problem is provided wherever possible.
To find the Mark and point release number of your library, call NAG routine
a00aac( ).
 Routines: c09aac, c09ccc and c09cdc
Synopsis: 
Multilevel wavelets cannot handle periodic end extension 
Description: 
When mode = Nag_Periodic and wtrans = Nag_MultiLevel the multilevel wavelet
transform routines do not work properly if n is not a power of 2.

Severity: 
Noncritical 
Problem since Mark: 
9.0 
Fixed in Mark: 
23.0 
Workaround: 
The option combination of a multilevel wavelet transform using a
periodic end extension is disallowed; a call to the initialization
routine c09aac with this combination will return with an error code.
For multilevel analysis of periodic data, you are advised to experiment
with alternative end conditions; the periodic property of the data can
also be used to extend the data set in both directions to points that better
suit the alternative end condition (e.g. extend the data to next maximum or minimum). 
 Routines: d06aac, d06abc and d06acc
Synopsis: 
Stack size or thread safety problems may be observed with some d06 routines 
Description: 
d06aac, d06abc and d06acc contain large local arrays that may cause stack
size and/or thread safety problems. 
Severity: 
Critical 
Problem since Mark: 
7.0 
Fixed in Mark: 
23.3 
Workaround: 
Do not use these routines in a multithreaded environment. For serial
execution, set stack size limit to 10MB or greater. 
 Routine: e04nqc
Synopsis: 
Internal file overflow 
Description: 
If you set a New Basis File in e04nqc, e04vhc or e04wdc and your total
problem size (n + m, n + nf or
n + nclin + ncnln, respectively)
is greater than 80 you will experience an internal buffer overflow
and possible program crash.

Severity: 
Critical 
Problem since Mark: 
9.0 
Fixed in Mark: 
23.0 
Workaround: 
Unfortunately there is no convenient workaround. The only way to
avoid this crash is to not specify a New Basis File or to
have a small enough problem.

 Routines: e04vhc and others
Synopsis: 
Usersupplied character strings containing spaces may cause garbled error messages 
Description: 
Some routines produce error messages containing char data that has been
supplied through the argument list by the user. An example is e04vhc,
where the xnames or fnames can be referred to in error
messages. Having spaces in these strings confuses the internal
errormessage splitter, which splits on spaces. Thus, error messages
returned by the routine may be garbled. 
Severity: 
Noncritical 
Problem since Mark: 
Various (routinedependent) 
Fixed in Mark: 
23.0 
Workaround: 
Make sure userprovided char data is without spaces. 
 Routine: e05ucc
Synopsis: 
An unhelpful error exit is returned if e05ucc is called with incorrectly initialized optional argument arrays iopts and opts. 
Description: 
Function e05ucc return NE_INTERNAL_ERROR if e05ucc is called without previously having called e05zkc with argument "Initialize = e05ucc".

Severity: 
Noncritical 
Problem since Mark: 
23.0 
Fixed in Mark: 
24.0 
Workaround: 
Call e05zkc with argument "Initialize = e05ucc" before calling e05ucc. 
 Routines: f16rbc and f16ubc
Synopsis: 
f16rbc and f16ubc return 0 if kl or ku is 0, instead of the correct norm.
pdab is incorrectly forced to be at least m when m==n 
Description: 
f16rbc and f16ubc mistakenly make a quick return if kl or ku is 0,
instead of computing the correct value for the requested norm.
Also, pdab is incorrectly forced to be at least m when m==n. 
Severity: 
Critical 
Problem since Mark: 
9.0 
Fixed in Mark: 
23.0 
Workaround: 
If kl or ku is 0, use the general matrixnorm routines f16rac or
f16uac, with the input matrix in full storage. If m==n, make sure
that pdab>=m. 
 Routine: g02qgc
Synopsis: 
Returns incorrect results when ntau > 1 and user supplied
initial values for b are being used 
Description: 
If ntau > 1, the optional parameter
"Calculate Initial Values = No" is set, and
the rows of array b are not all identical,
then the results returned by g02qgc are incorrect. 
Severity: 
Critical 
Problem since Mark: 
23.0 
Fixed in Mark: 
24.0 
Workaround: 
Rather than call the routine once with ntau > 1, call the
routine multiple times with ntau = 1, analysing a different
value of tau on each call. 
Page generated on 20March2013

