Crash Course on Crashes
summary
Covers three concrete crash families—unrecognized selector, bad memory access (NSZombies) and watchdog kills from fast allocations—and shows exact debugging steps: add Swift/Objective‑C/general breakpoints, create symbolic breakpoints or temporary method stubs to trap missing selectors, enable Zombies in the Run scheme to catch use‑after‑free, and run Instruments (Zombies, Allocations, CPU) to find rapid leaks or spikes. Also details collecting logs via Xcode device logs and Organizer, preserving dSYMs, and using symbolicatecrash or crash SDKs (Crashlytics/Hockey) plus a demo project on GitHub.
AI-written summary · about
chapters (19)
- 0:00Start
- 3:49Common Reasons for Crashes To Happen
- 7:35Breakpoints
- 7:50General Exception Breakpoint
- 8:20Adding Breakpoints
- 9:33Symbolic Breakpoints and Extensions
- 10:11Adding an Extension
- 12:22Bad Memory Access
- 13:55Memory Management in Objective C in Ios
- 24:13Monitoring the Xcode Session Debugging
- 24:38Good Practices To Handle Crashes
- 25:43Get Familiar with Instruments
- 26:07Apple Tech Note
- 27:43Threaded Crashes
- 28:07The Stack Race
- 30:51Export the Developer Directory
- 32:02Collecting those Crash Logs
- 32:30Grab a Crash Log of a Device
- 33:12Grab Crash Logs from Itunes Connect
related talks
50mAn Exploration of Debugging Techniques and Tools
03mLevel up your game’s stability with Crashlytics
15mCrashlytics for game developers
23mMobile App Crashes in Production: Lessons Learned from a Tester’s Viewpoint
52mNobody Can Program Correctly - Lessons From 20 Years of Debugging C++ Code
20mDiscover memory leaks with Testcase
37mLeakCanary, then what? Nuking Nasty Memory Leaks
01h 01mBack to Basics: Debugging in Cpp