https://bugs.openldap.org/show_bug.cgi?id=8361
Howard Chu hyc@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED
--- Comment #2 from Howard Chu hyc@openldap.org --- Unix case is a non-issue. libc only does the `sprintf(buf, "Error %d", err)` fallback for error codes it doesn't recognize. These only occur when an old libc is running on a newer kernel version (that happens to define new errno values). So in practice it only happens with extremely old statically linked binaries running on a much newer system.
The Windows situation is a bit cleaner now that we're not using as many libc error codes. (ITS#8192). In most cases none of that will matter. Also most error messages are short, generally shorter than one 80 column line. Not worth worrying about.