gd_error man page

gd_error, gd_error_string — report a GetData library error

Synopsis

#include <getdata.h>

int gd_error(const DIRFILE *dirfile);

char *gd_error_string(const DIRFILE *dirfile, char *buffer, size_t buflen);

Description

The gd_error() function determines the success or failure of the most recent GetData library function call that operated on dirfile. If the last call succeeded, gd_error() will return GD_E_OK (which equals zero).  If the last call failed, gd_error() returns a negative-valued error code indicating the cause of the failure. Possible codes vary from function to function.  See corresponding manual page of the function that failed for a list of possible codes.

The gd_error_string() function behaves similarly, but composes a string describing the error.  If buffer is not NULL, the string is written to this memory location.  At most buflen characters will be written including the terminating NUL byte.  If buffer is not large enough to hold the entire string, the string will be truncated, but the truncated string will still be NUL-terminated.

If buffer is NULL, gd_error_string() will allocate a string of sufficient length on the heap.  In this case, buflen is ignored.  By default, malloc(3) is used to allocate this buffer, but an alternate memory manager may be specified by calling gd_alloc_funcs(3) before calling this function.  The caller is responsible for deallocating this string when it is no longer needed.

The functions gd_alloc_funcs(3), gd_error_count(3), gd_flags(3), gd_free_entry_strings(3), gd_mplex_lookback(3), and gd_parser_callback(3) are ignored by these functions, since they always succeed.  Previous gd_error() and gd_error_string() calls are also ignored.

Return Value

The gd_error() function always returns the integer error code of the last library call on the supplied DIRFILE object.

If buffer is non-NULL, gd_error_string() returns buffer, unless buflen is less than one, in which case it returns NULL.  If buffer is NULL, this function returns a newly allocated string of sufficient length which should be deallocated by the caller, or NULL, if memory allocation failed.

History

The get_error_string() function appeared in GetData-0.3.0.

The get_error() function appeared in GetData-0.4.0.  Before this, the error code was directly accessible via the dirfile->error member in the DIRFILE structure.

In GetData-0.7.0, these functions were renamed to gd_error() and gd_error_string(). This is also the first release in which gd_error_string() would allocate a buffer for the error string if passed NULL.

See Also

gd_error_count(3)

Referenced By

gd_add(3), gd_add_alias(3), gd_add_bit(3), gd_add_spec(3), gd_aliases(3), gd_alias_target(3), gd_alloc_funcs(3), gd_alter_affixes(3), gd_alter_bit(3), gd_alter_encoding(3), gd_alter_endianness(3), gd_alter_entry(3), gd_alter_frameoffset(3), gd_alter_protection(3), gd_alter_spec(3), gd_array_len(3), gd_bof(3), gd_carrays(3), gd_close(3), gd_constants(3), gd_delete(3), gd_desync(3), gd_dirfilename(3), gd_dirfile_standards(3), gd_encoding(3), gd_endianness(3), gd_entry(3), gd_entry_list(3), gd_entry_type(3), gd_eof(3), gd_error_count(3), gd_flags(3), gd_flush(3), gd_fragment_affixes(3), gd_fragment_index(3), gd_fragmentname(3), gd_fragment_namespace(3), gd_framenum_subset(3), gd_frameoffset(3), gd_get_carray_slice(3), gd_getdata(3), gd_get_sarray_slice(3), gd_get_string(3), gd_hidden(3), gd_hide(3), gd_include(3), gd_invalid_dirfile(3), gd_linterp_tablename(3), gd_madd_bit(3), gd_match_entries(3), gd_metaflush(3), gd_move(3), gd_naliases(3), gd_native_type(3), gd_nentries(3), gd_nfragments(3), gd_nframes(3), gd_open(3), gd_parent_fragment(3), gd_protection(3), gd_put_carray_slice(3), gd_putdata(3), gd_put_sarray_slice(3), gd_put_string(3), gd_raw_filename(3), gd_reference(3), gd_rename(3), gd_rewrite_fragment(3), gd_sarrays(3), gd_seek(3), gd_spf(3), gd_strings(3), gd_strtok(3), gd_tell(3), gd_uninclude(3), gd_validate(3), gd_verbose_prefix(3).

25 December 2016 Version 0.10.0 GETDATA