On Fri, Sep 29, 2023 at 09:50:53AM +0200, Mark Brown wrote:
On Thu, Sep 28, 2023 at 05:48:22PM -0700, Kees Cook wrote:
nolibc doesn't have a strerror() and adding the table of strings required doesn't seem like a good fit for what it's trying to do so when we're using that only print the errno.
Oh, interesting... what environment ends up without strerror()?
Like I say it's for nolibc - it's just some header files (all in the kernel source), while it generally aims to be libc compatible it's intentionally very small.
Right, I mean, how would one normally encounter this environment? Running the selftests on m68k userspace or something?