I have been troubleshooting this script for weeks and finally found it was trying to divide by zero.
- Marxism-Fennekinism ( @HiddenLayer5@lemmy.ml ) 8•1 year ago
Just ship it with debug flags so your program always generates a stack trace to the user!
- raubarno ( @raubarno@lemmy.ml ) 5•1 year ago
Panicking on the error is much better than letting the system work continue on an undefined behaviour (good luck with debugging if you are ignoring all assertions)!
- elouboub ( @elouboub@kbin.social ) 4•1 year ago
Makes me think of devs who debug with print statements instead of a debugger and breakpoints.
- lens_r ( @lens_r@kbin.social ) 7•1 year ago
IMO there’s a place for both. A print statement will reveal a flaw in the programmer’s thinking regarding the control flow of the program and the state at that time. If a print statement gives something unexpected, you know exactly where to look in the debugger. If it gives you what you expected, it reveals the problem may be elsewhere
- Fabiozeh ( @Fabiozeh@lemmy.world ) 4•1 year ago
Well, Kernighan himself said “The most effective debugging tool is still careful thought, coupled with judiciously placed print statements.”
If it was good enough for him…
- erbs ( @erbs@lemmy.ml ) 3•1 year ago
/me glances sideways at codebase
- taylus ( @taylus@lemmy.ml ) 3•1 year ago
would it help if I returned -2147483648?