293

Console Logs : Hello from the other side (lemmy.world)

submitted 2 years ago* (last edited 2 years ago) by alphacyberranger@lemmy.world to c/programmer_humor@programming.dev

14 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] deegeese@sopuli.xyz 15 points 2 years ago

When the issue is only seen after hours of runtime, logging is more practical.

[-] Chreutz@lemmy.world 7 points 2 years ago

I recently had an issue that happens on one out of between ten thousand and a hundred thousand interactions between two embedded processors. Thank god for logging!

[-] o11c@programming.dev 6 points 2 years ago

Even logging can sometimes be enough to hide the heisgenbug.

Logging to a file descriptor can sometimes be avoided by logging to memory (which for crash-safety includes the possibility of an mmap'ed file, since the kernel will just take care of them as long as the whole system doesn't go down). But logging from every thread to a single section of memory can also be problematic (even without mutexes, atomics can be expensive and certainly have side-effects) - sometimes you need a separate per-thread log, and combine in the log-reader tool.

[-] marcos@lemmy.world 3 points 2 years ago

Well, conditional breakpoints exist.

But use whatever is easiest. People trying to micromanage how others use computers are the worst. And on the most popular languages by job count, your debuggers isn't all that more powerful than a well-constructed log anyway. (Hell, the people insisting that others adopt better tools should start with the language.)