Summary
In this chapter, we looked at many ways to debug applications that are misbehaving, in addition to learning some ways to check on the overall health of the app. First, we looked at some basic debugging practices such as printing, using breakpoints, and understanding the call stack. Then we looked at some advanced debugging tools like Address Sanitization, which helped us solve hard to find bugs in C and Objective-C code. We also learned about the performance gauges in the debug navigator, which help us stay alert to any major issues that don't necessarily cause a crash. Finally, we looked at the View Debugger, which helps us visualize any bugs that we may have in our view hierarchies.
In the next chapter, we'll be looking at some of the ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access