1957 return wcs.err->status;
1960 In
this example,
if an error was generated in one of the
prjset() functions,
1961 wcsperr() would print an error traceback starting with
wcsset(), then
1962 celset(), and finally the particular projection-setting function that
1963 generated the error. For each of them it would print the status return value,
1964 function name, source file, line number, and an error message which may be
1965 more specific and informative than the general error messages reported in the
1966 first example. For example, in response to a deliberately generated error,
1967 the @c twcs test program, which tests
wcserr among other things, produces a
1968 traceback similar to this:
1970 ERROR 5 in wcsset() at line 1564 of file wcs.c:
1971 Invalid parameter value.
1972 ERROR 2 in celset() at line 196 of file cel.c:
1973 Invalid projection parameters.
1974 ERROR 2 in
bonset() at line 5727 of file prj.c:
1975 Invalid parameters for Bonne's projection.
1978 Each of the @ref structs "structs" in @ref overview "WCSLIB" includes a
1979 pointer, called @a err, to a
wcserr struct. When an error occurs, a struct is
1980 allocated and error information stored in it. The
wcserr pointers and the
1981 @ref memory "memory" allocated for them are managed by the routines that
1985 example above. If enabled, when an error occurs it is the user's
1986 responsibility to free the memory allocated for the error message using
1988 out of scope will result in memory leaks (if execution continues beyond the