4 ms·
Eh Segfaults are like the easiest error to debug, they almost always tell you exactly where the problem is.
by TinkersW 2y ago
Eh Segfaults are like the easiest error to debug, they almost always tell you exactly where the problem is.
- relistan 2y agoExcept when they don’t. I’m debugging something right now that runs fine under debugging conditions and crashes with a segfault in real life. It’s not randomized memory (messed with that), it’s likely some race where the timing is changed by the debugger.
- bamboozled 2y agoruns fine under debugging conditions and crashes with a segfault in real life There's your clue right there...
- relistan 2y agoYes. Did you read what I wrote?
- randomNumber7 2y agoAdressSanitizer is an absolute gamechanger and should amost always spare you the effort of the nightmare debugging of undefined behaviour.