ARES_FREE_DATA(3)

💖 ARES_FREE_DATA(3) 💖

okay bestie, gather round, we're doing memory management and we're doing it cutely. this is a page from the Library Functions Manual, and it's all about ares_free_data — the lil cleanup queen of the c-ares world. she doesn't build anything, she doesn't fetch anything, she just frees stuff. and honestly? iconic behaviour.

✨ NAME ✨

ares_free_data — free data allocated by several c-ares functions 🧹💅

🌸 SYNOPSIS 🌸

#include <ares.h>

void ares_free_data(void *dataptr)

🦋 DESCRIPTION 🦋

so, ares_free_data(3) frees one or more data structures that were allocated and handed back to you by several c-ares functions. no cap, if you got a pointer from one of the functions on this list, you must deallocate it using this function. not free(), not vibes, not hoping the OS forgives you. this one. periodt.

• ares_get_servers(3) — when you use it to free the data returned by ares_get_servers(3), this will free the whole linked list of ares_addr_node structures that ares_get_servers(3) returned. the entire chain, gone, slay.
• ares_parse_srv_reply(3) — when you use it to free the data returned by ares_parse_srv_reply(3), this will free the whole linked list of ares_srv_reply structures that ares_parse_srv_reply(3) returned, along with any additional storage associated with those structures. yes bestie, the extra storage too, she's thorough like that.
• ares_parse_mx_reply(3) — when you use it to free the data returned by ares_parse_mx_reply(3), this will free the whole linked list of ares_mx_reply structures that ares_parse_mx_reply(3) returned, along with any additional storage associated with those structures. mwah, spotless.
• ares_parse_txt_reply(3) — when you use it to free the data returned by ares_parse_txt_reply(3), this will free the whole linked list of ares_txt_reply structures that ares_parse_txt_reply(3) returned, along with any additional storage associated with those structures. every last crumb 💜
• ares_parse_soa_reply(3) — when you use it to free the data returned by ares_parse_soa_reply(3), this will free the ares_soa_reply structure, along with any additional storage associated with that structure.
• ares_parse_uri_reply(3) — when you use it to free the data returned by ares_parse_uri_reply(3), this will free the list of ares_uri_reply structures, along with any additional storage associated with those structures.

ngl, that SOA and URI entry were cuddled up together in the original text like two besties sharing a blanket. i gave them their own bullets so your eyes don't have to work that hard. same facts, better vibes 🫶

⭐ RETURN VALUE ⭐

ares_free_data(3) does not return a value. that's it. nothing comes back. she takes and she takes and she leaves silently like a main character exiting a party. no return value, no drama. 💀

🌈 AVAILABILITY 🌈

this function was first introduced in c-ares version 1.7.0. so if you're on something older than that, bestie… the function simply isn't there. manifesting an upgrade for you ✨

👑 SEE ALSO 👑

ares_get_servers(3), ares_parse_srv_reply(3), ares_parse_mx_reply(3), ares_parse_txt_reply(3), ares_parse_soa_reply(3)

and that's the whole page, bestie!! 🎀 this version of the c-ares docs is dated 5 March 2010 — yeah, she's an elder but she still ate — and it comes to you courtesy of the c-ares crew. go forth, free your linked lists, and remember: every pointer you allocate deserves its goodbye kiss 💖✨