3 ms·
This "print debugging is bad" idea never made sense. Debugging is largely an effort to understand what's going on inside a program - having the program "talk ba
by FartyMcFarter 8y ago
This "print debugging is bad" idea never made sense. Debugging is largely an effort to understand what's going on inside a program - having the program "talk back" to you via prints can be a great way to do this.
Sometimes, print debugging is the only practical way to fix a bug. For example, very rare bugs which can only be reproduced by running many instances of the code for a long time, or situations where attaching a debugger is not feasible (as in live services).
- pjmlp 8y agoThen one uses trace points like IntelliTrace or DTrace.
- majewsky 8y agoDoes this also work with 10 replicas of something in Alpine containers on clusters spread across different regions?
- pjmlp 8y agoIntelliTrace works perfectly fine on Windows clusters and across Cloud deployments on Azure. Never used Alpine containers, so no idea how it works with DTrace / SystemTap. However a quick web search revealed the following right away, surely there are other results available. "Systemtap for CoreOS Container Linux" https://medium.com/makingtuenti/systemtap-for-coreos-container-linux-b2c0a0b5dce3 https://medium.com/makingtuenti/systemtap-for-coreos-contain... "App Trace Roll: Users Guide" . For Red Hat Linux clusters https://docs.huihoo.com/rocksclusters/app-trace/4.1/index.html https://docs.huihoo.com/rocksclusters/app-trace/4.1/index.ht...