Nah it would just hallucinate this error all the time
Findecanor•May 25, 2026
It would hallucinate error codes that don't exist.
andai•May 25, 2026
I often ran into an error where multimodal models would refuse to operate in transcription mode due to some system prompt.
cat-whisperer•May 25, 2026
what about ETHOS : Error it's Mythos? lol!
tetha•May 25, 2026
ETHOS is generally reserved for a certain type of error involving slab memory and complex logic though.
Let's hope that reference is not too obscure...
chuckadams•May 25, 2026
#define ETERNITY 999 /* stuck in thinking loop */
JSR_FDED•May 25, 2026
#define EKNOWBETTER 231 # ignoring prompt
chme•May 25, 2026
#define EPROCRASTINATE 245 /* exhausted all output tokens with reasoning */
aaronmdjones•May 25, 2026
`errno` is a userland concept; the kernel returns negative error numbers that libc then turns into -1 and sets errno. Thus the correct manpage is errno(3).
eqvinox•May 25, 2026
OpenBSD up to 5.9 had errno(2) symlinked to intro(2), describing error codes:
Also, your statements about the kernel and libc are OS specific.
WhyNotHugo•May 25, 2026
Why does libc do this instead of simply returning that same negative number?
rcxdude•May 25, 2026
POSIX, basically. It was already a convention by the time linux/glibc implemented it.
cluckindan•May 25, 2026
207 is a bald move
cold_harbor•May 25, 2026
#define ESYCOPHANT 200 /* user asserted 2+2=5; model concurred */
OhMeadhbh•May 25, 2026
As a long time emacs user, I appreciated the inclusion of EMACS as an error code. When I moved from TECO to gnu emacs in to 80s, elisp was an advance. Now I have a perpetual todo item... "rewrite emacs in fennel or janet or even minimalisp."
11 Comments
If only AI threw an error when it hallucinates.
Let's hope that reference is not too obscure...
https://man.freebsd.org/cgi/man.cgi?query=errno&apropos=0&se...
Also, your statements about the kernel and libc are OS specific.
"What was deluxe is now debris..."