gensio_err(3)

πŸ“¦
version 3.0.4 Β· 2 versions
  • 3.0.4 Β· alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, debian trixie, epel 9, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 2.6.2 Β· debian bookworm, ubuntu jammy
, in alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, debian trixie, epel 9, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– gensio_err β€” error reporting values for gensio functions πŸ’–

okay bestie, we're in the Library Functions Manual section and this is the page about all the little error codes gensio throws at you. no cap, it's lowkey the most important list you'll ever read. ✨


🌸 NAME 🌸

gensio_err β€” error reporting values for gensio functions


πŸ¦‹ SYNOPSIS πŸ¦‹

#include <gensio/gensio_err.h>
const char *gensio_err_to_str(int err)

✨ DESCRIPTION ✨

so here's the tea πŸ«–: every gensio function that returns an error, and every value that shows up in a callback from the gensio library, is handing you a gensio error. that's it, that's the whole vibe. possible values are:

  • GE_NOERR β€” no error πŸ’…
  • GE_NOMEM β€” out of memory 😭
  • GE_NOTSUP β€” operation not supported πŸ™…
  • GE_INVAL β€” invalid data to parameter
  • GE_NOTFOUND β€” value or file not found πŸ”
  • GE_EXISTS β€” value already exists
  • GE_OUTOFRANGE β€” value out of range
  • GE_INCONSISTENT β€” parameters inconsistent in call
  • GE_NODATA β€” no data was available for the function
  • GE_OSERR β€” OS error, see logs πŸ‘€
  • GE_INUSE β€” object was already in use
  • GE_INPROGRESS β€” operation is in progress ⏳
  • GE_NOTREADY β€” object was not ready for operation
  • GE_TOOBIG β€” value was too large for data
  • GE_TIMEDOUT β€” operation timed out βŒ›
  • GE_RETRY β€” retry operation later πŸ”
  • GE_KEYNOTFOUND β€” unable to find the given key πŸ”‘
  • GE_CERTREVOKED β€” key was revoked
  • GE_CERTEXPIRED β€” key was expired
  • GE_KEYINVALID β€” key is not valid
  • GE_NOCERT β€” certificate not provided
  • GE_CERTINVALID β€” certificate is not valid
  • GE_PROTOERR β€” protocol error
  • GE_COMMERR β€” communication error πŸ“‘
  • GE_IOERR β€” internal I/O error
  • GE_REMCLOSE β€” remote end closed connection πŸ‘‹
  • GE_HOSTDOWN β€” host could not be reached
  • GE_CONNREFUSE β€” connection refused 🚫
  • GE_DATAMISSING β€” data was missing
  • GE_CERTNOTFOUND β€” unable to find given certificate
  • GE_AUTHREJECT β€” authentication tokens rejected
  • GE_ADDRINUSE β€” address already in use
  • GE_INTERRUPTED β€” operation was interrupted by a signal ⚑
  • GE_SHUTDOWN β€” operation on shutdown file descriptor
  • GE_LOCALCLOSED β€” local side closed connection
  • GE_PERM β€” permission denied πŸ™ˆ
  • GE_APPERR β€” application error
  • GE_UNKNOWN_NAME_ERROR β€” unknown name server lookup failure
  • GE_NAME_ERROR β€” unable to find a valid name on the name server
  • GE_NAME_SERVER_FAILURE β€” serious name server failure πŸ’€
  • GE_NAME_INVALID β€” invalid name server information
  • GE_NAME_NET_NOT_UP β€” network address for the given name is not available

and then there's gensio_err_to_str, which is the glow-up function: it converts an integer error value into the given string. so you can actually read what went wrong instead of staring at a number like it's a cryptic text from your ex. iconic behavior, honestly. πŸ‘‘


πŸ‘‘ SEE ALSO πŸ‘‘

gensio(5), gensio_err(3), gensio_log(3)


that's the whole page, bestie!! go forth and handle your errors with main character energy πŸ’œ

this was the gensio_err(3) page from the Library Functions Manual, dated 24 Feb 2019 β€” mwah, love u, bye πŸŽ€

πŸ“¦ where this page comes from