globus_ope...or_utility(3)

πŸ“¦
version 4.4 Β· 5 versions
, in epel 10, fedora 43, fedora 44, ubuntu resolute, ubuntu stonking

πŸ’– globus_openssl_error_utility β€” Error Object Helper Functions πŸ’–

okay bestie, come closer, we're doing globus_ope...or_utility(3) from the Library Functions Manual today and honestly? it's giving niche-but-iconic ✨

🌸 NAME 🌸

globus_openssl_error_utility β€” Error Object Helper Functions πŸ’…

  • Error Object Helper Functions.

πŸ¦‹ SYNOPSIS πŸ¦‹

Functions

globus_bool_t globus_error_match_openssl_error (globus_object_t *error,
    unsigned long library, unsigned long function, unsigned long reason)

globus_object_t * globus_error_wrap_openssl_error
    (globus_module_descriptor_t *base_source, int error_type, const char
    *source_file, const char *source_func, int source_line, const char
    *format,...)

✨ Detailed Description ✨

Error Object Helper Functions πŸ’–

so the functions in the Error Object Helper Functions section are the ones that deal with Globus error objects built out of OpenSSL error data. literally what they do is manipulate the generic globus_object_t representation of an OpenSSL error. that's the whole vibe, no cap 🫢


πŸ‘‘ Function Documentation πŸ‘‘

🌈 globus_bool_t globus_error_match_openssl_error (globus_object_t * error, unsigned long library, unsigned long function, unsigned long reason)

Check whether the error originated from a specific library, from a specific function and is of a specific type. πŸ’…

this one checks whether the error β€” or any of its causative errors β€” originated from a specific library, a specific function, and is of a specific type. it goes digging through the whole little error family tree, fr fr 🌳

Parameters

  • error β€” The error object for which to perform the check
  • library β€” The library to check for
  • function β€” The function to check for
  • reason β€” The type to check for

Return values

  • GLOBUS_TRUE β€” Error matched πŸ”₯
  • GLOBUS_FALSE β€” Error failed to match 😭

πŸŽ€ globus_object_t * globus_error_wrap_openssl_error (globus_module_descriptor_t * base_source, int error_type, const char * source_file, const char * source_func, int source_line, const char * format, ...)

Wrap the OpenSSL error and create a wrapped globus error object from the error. πŸ¦‹

this function gets all the OpenSSL errors out of the error list, and chains them together using the globus error string object. and the resulting globus error object? it's a wrapper to the OpenSSL error sitting at the end of the chain. the way that it just collects them all and links them up… obsessed ✨

Parameters

  • base_source β€” The module that the error was generated from
  • error_type β€” The type of error encapsulating the OpenSSL error
  • source_file β€” Name of file. Use FILE
  • source_func β€” Name of function. Use _globus_func_name and declare your func with GlobusFuncName(<name>)
  • source_line β€” Line number. Use LINE
  • format β€” format string for the description of the error entry point where the OpenSSL error occurred, should be followed by parameters to fill the format string (like in printf).

Returns

The globus error object. A globus_result_t object can be created using the globus_error_put function πŸ’œ

See also

globus_error_put()

not me pointing out that these param descriptions are doing the most with capital letters, but bestie, copy them exactly like that, iykyk πŸ’€

🌟 Author 🌟

Generated automatically by Doxygen for globus_gsi_openssl_error from the source code. πŸ€–βœ¨


and that's the whole page, bestie, we ate and left absolutely zero crumbs πŸ“

signing off from the globus_gsi_openssl_error era, Version 4.4 πŸŽ€ mwah πŸ’