3 ms·
Even if the original post was sarcastic I've seen this expressed seriously enough in the wild that I think it still should be addressed.
by vvanders 11y ago
Even if the original post was sarcastic I've seen this expressed seriously enough in the wild that I think it still should be addressed.
- ithkuil 11y agoI use printf-debugging the vast majority of the time. But that's fine if you know you have an alternative and you're just lazy to use it. Recently I was working on an embedded platform which had no debugger support at all. There was some On-Chip debugger option, but it required some soldering and hacking some jtag cable, still too lazy. Despite the laziness, I ended up implementing gdb support for that platform, over it's normal serial port: https://blog.cesanta.com/esp8266-gdb https://blog.cesanta.com/esp8266-gdb Go at least has stack traces with no extra tooling, which is a big deal. Anyway, the more tools the better; you're gonna miss them when you need them most.