KVM_GETERR(3)

💖 KVM_GETERR(3) — Library Functions Manual 💖

okay so bestie, this is the libkvm page for kvm_geterr — yes, the “get error message on kvm descriptor” one. it’s giving error-message retrieval and honestly it ate. 🫶

🌸 NAME 🌸

kvm_geterr — get error message on kvm descriptor

📚 LIBRARY 📚

Kernel Data Access Library (libkvm, -lkvm)

✨ SYNOPSIS ✨

#include <kvm.h>

char *
kvm_geterr(kvm_t *kd);

💅 DESCRIPTION 💅

okay so kvm_geterr(kvm_t *kd) is the friend you call when you need the tea on what just went wrong. she returns a string describing the most recent error condition on the descriptor kd. main character energy, fr fr.

⚠️ The results are undefined if the most recent kvm(3) library call did not produce an error. so like, don’t just call her for fun and expect a valid message — that’s the vibe check.

and the way that the returned string is stored in memory owned by kvm(3)? yeah, so if you need to keep the message around, copy it out and save it elsewhere if necessary — the original is not yours to keep. periodt.

🎀 RETURN VALUES 🎀

the function kvm_geterr() will return "" if kd is NULL or an error has not been captured for kd. that’s the whole return-value situation, no cap. 💖

🦋 SEE ALSO 🦋

• kvm(3)
• kvm_close(3)
• kvm_getargv(3)
• kvm_getenvv(3)
• kvm_getprocs(3)
• kvm_nlist(3)
• kvm_open(3)
• kvm_openfiles(3)
• kvm_read(3)
• kvm_write(3)

💀 BUGS 💀

ngl, there’s a real catch here. this routine cannot be used to access error conditions due to a failed kvm_openfiles() call, since failure is indicated by returning a NULL descriptor. so errors on open are output to the special error buffer passed to kvm_openfiles(). This option is not available to kvm_open().

xoxo, this page’s footer energy is Debian, March 21, 2017, KVM_GETERR(3) 💖