Dan PiponiRevisiting a book I read when I was a kid. Published in 1971, when computers could "make nearly a million additions every second" and presumably intended for young children, it has a surprising amount of detail - eg. on how instructions are encoded in a word.
I've spent much of the last week trying to figure out how a simple recv() operation can corrupt data nowhere near the address provided as an argument. But this page - and I vaguely remember reading this as a kid - may have been the moment in my life when I first learnt that debugging was a thing.
BTW Having reduced the problem to having a random corruption as a result of a system call I have no idea how to proceed with debugging which is not a feeling I'm used to. Pretty sure it's not a kernel bug. Fairly sure it's not a compiler bug. I'm going to have to start considering supernatural explanations soon...
Simon Frankau@dpiponi My sympathy! No luck from the usual meta-advice ("rubber duck it" and "do something else for a while")?
Bart Wronski 🇺🇦🇵🇸@dpiponi I don't know what is more painful here - old-time sexism (and yes, I know it wasn't considered sexism back then!) or the bad sitting posture :)