Who controls glibc? [LWN.net]

Who controls glibc?

Posted May 7, 2018 20:22 UTC (Mon) by lsl (subscriber, #86508)
In reply to: Who controls glibc? by amk
Parent article: Who controls glibc?

That depends, I guess. The "fucking Sun..." message might be unique within the kernel code so a grep brings you right to the correct source location. Strings complaining about unexpected endianness may show up often enough to be useless.

to post comments

Who controls glibc?

Posted May 7, 2018 22:23 UTC (Mon) by k8to (guest, #15413) [Link] (2 responses)

My very very boring solution to this problem is to ensure that each site where you would emit an error has very minor variations in expression. Usually I try to make this be further information: "wrong endianness encountered in xxx" Here xxx sometimes isn't very user-digestible, but I try to make the first portion of the error as explicitly informative as possible and potentially put the xxx in parenthesis or similar. However, I have been known to use trivially different wording when the xxx approach isn't available.

As a a user, I'd prefer xxx to be some punchy vulgarity, but I think I'm in the minority.

Who controls glibc?

Posted May 14, 2018 21:46 UTC (Mon) by cpitrat (subscriber, #116459) [Link] (1 responses)

Or make __FILE__ and __LINE__ be part of your log ...

Who controls glibc?

Posted May 27, 2018 11:03 UTC (Sun) by k8to (guest, #15413) [Link]

In commercial environments, there's often pressure not to show these "internal details" to users.