News for hackers. Stuff that matters.
Re:Rust 1.32 released by FartyMcFarter on Thursday January 17, 2019 @06:11PM (#18935554)
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).

Re:Rust 1.32 released by pjmlp on Friday January 18, 2019 @01:29AM (#18937435)
Then one uses trace points like IntelliTrace or DTrace.
Re:Rust 1.32 released by majewsky on Friday January 18, 2019 @06:50AM (#18938651)
Does this also work with 10 replicas of something in Alpine containers on clusters spread across different regions?
Re:Rust 1.32 released by pjmlp on Friday January 18, 2019 @07:02AM (#18938698)
IntelliTrace 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-contain...

"App Trace Roll: Users Guide" . For Red Hat Linux clusters

https://docs.huihoo.com/rocksclusters/app-trace/4.1/index.ht...