The debugging mindset
summary
Debugging becomes a methodical loop: inspect Process Explorer to find three processes, scan 3–4k-line logs for IPC pipe disconnect errors, decompile the .NET assembly with decompile .NET with dotPeek and recompile a quick patch, observe assembly sizes (273 KB vs 287 KB) and block updater by removing write permissions, build a small console using the app’s IPC library to extend IPC logging, discover the 3000 ms timeout in minified main.js, change it to 60 s, and the app starts — the end-to-end workaround actually works after a few hours.
AI-written summary · about
chapters (22)
- 0:00Introduction to debugging
- 1:16Debugging is not about tools
- 2:44Gaining data during investigations
- 4:30Lazy and creative debugging
- 6:40Investigation begins with Twitch app
- 7:24Exploring application files
- 9:10Analyzing logs for errors
- 12:03Decompiling and testing theories
- 18:15Fixing the Java exception
- 21:07Bypassing auto-updater restrictions
- 22:54New exception and shutdown issue
- 24:41Investigating IPC connection failures
- 28:19Stuck and seeking help
- 29:02Building a custom IPC test app
- 33:19Testing IPC communication
- 37:21Activating detailed IPC logs
- 41:30Synchronous IPC connection test
- 43:19Comparing main and child process logs
- 46:58Decompiling Electron application
- 51:19Final fix and testing
- 52:02Key takeaways from debugging
- 53:28Q&A session
related talks
38mFrom the Exorcist to Hercule Poirot
54mDebugging Effectively
41mDebug like a scientist
53mTools and practices to help you deal with legacy code
37mThe Bright Future of Debuggers: Challenges and Opportunities
26mThe Mindset of Debugging
01h 01mBeyond step-by step debugging in Visual Studio
17mFast Focus: Visual Studio Debugging & Diagnostics: Tips & Tricks