__libc_fatal public version?

Cristian Rodríguez cr@cristianrodriguez.net
Tue Dec 30 14:07:47 GMT 2025


Hi:

Many, many low level software requires exactly what __libc_fatal does,
a way to fail catastrophically with a message in any context.. (well
in almost any context as long mmap is able to get some virtual memory)
All the other ways are not as-safe, applications cannot count on them
been usable in signal handlers for example

Would it be possible that you will consider either :

- export this to userspace or
- extend the "error" api, something like error_ss , warn_ss or if all
that is too much
- implement the equivalent to the netbsd libc functions snprintf_ss,
vsnprintf_ss
  and leave the implementation of the rest of the code to applications
providing an example use im the documentation?

Thanks for reading..


More information about the Libc-alpha mailing list