Interesting fork of rr to have time travel debugging with software counters. Hopefully will allow using rr in environments where it's limited by lack of access to hardware performance counters.
An excellent article, that troubleshooting skill is really important in many fields... In particular software engineering. It's hard to teach and learn but it makes all the difference.
Looks like a nice tool. Maybe it'll replace my trusty cgdb in some cases.
I very much agree with this. The relationship between developers and their frameworks is rarely healthy. I think the author misses an important advice though: read the code of your frameworks. When stuck invest sometime stepping into the frameworks with the debugger. Developers too often treat those as a black box.
Definitely a sound advice. You don't want to be confused when debugging something because it looks too much like a variable or a property name.
This is an important trait to have for a developer. If you're content of things working without knowing why and how they work, you're looking for a world of pain later.
How to avoid drowning in errors when getting serious about monitoring. Finding class of errors and treating them one by one will definitely help.
This is indeed a nice way to approach technical interviews. Unfortunately it requires quite some effort to setup and maintain. You also have to find the right bugs to put in the interview and this is a rarity.
You need to understand how core dumps work? This article is for you.
Nice little utility for Python programming. Helps to introspect on the spot.
Nice suite of tools. The eBPF based ones look promising.
Definitely this. In a world where LLM would actually be accurate and would never spit outright crappy code, programmers would still be needed. It'd mean spending less time writing but more time investigating and debugging the produced code.
Fascinating bug... the fine details of mundane protocols like SMTP can sometimes be surprising.
This can sometimes be confusing. Here are a couple of tips about debugging rpath and linker errors.
Looks like an interesting tool to analyze hard to reproduce bugs, especially when concurrency is involved. This could be useful to find the source of flaky tests as well.
Interesting debug tool for web frontend code. It'd be nice as a browser extension.
Nice tricks to debug the very early boot process, starting at PID 1. gdbserver saves the day here.
Definitely a weird one... still a mystery and unfortunately will probably stay this way. Having the code source could have helped nail it down, could have been interesting.
Interesting subtle differences between gzip and Python expectations which leads to a tough integration bug to find.
A few interesting tricks in there, the web platform definitely helps in term of tooling.