SCTP_FREEPADDRS(3)

πŸ“¦
version 15.1 Β· 2 versions
, in freebsd 15.1

πŸ’– NAME πŸ’–

okay so bestie, meet sctp_freepaddrs, sctp_freeladdrs β€” release the memory returned from a previous call. That’s the whole assignment, and they ate. πŸ’…


πŸ“š LIBRARY πŸ“š

These live in the Standard C Library (libc, -lc), periodt. 🫢


✨ SYNOPSIS ✨

Grab these headers first, bestie:

#include <sys/types.h>
#include <sys/socket.h>
#include <netinet/sctp.h>

void
sctp_freepaddrs(struct sockaddr *);

void
sctp_freeladdrs(struct sockaddr *);

πŸ¦‹ DESCRIPTION πŸ¦‹

So here’s the tea: the sctp_freepaddrs() and sctp_freeladdrs() functions are used to release the memory allocated by previous calls to sctp_getpaddrs() or sctp_getladdrs() respectively. Match them up correctly, iykyk β€” paddrs with getpaddrs, laddrs with getladdrs. πŸŽ€


🌸 RETURN VALUES 🌸

none.

Literally no return value, bestie. It’s giving void energy. 😭


🌈 SEE ALSO 🌈


πŸ‘‘ STANDARDS πŸ‘‘

The sctp_freepaddrs() and sctp_freeladdrs() functions conform to RFC 6458. Iconic behavior, no cap. ✨


and that’s the page, bestie β€” this one came from Debian, dated February 2, 2024, with the page tag SCTP_FREEPADDRS(3) πŸ«ΆπŸ’–

πŸ“¦ where this page comes from
  • freebsd 15.1: base 15.1
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms