3. Reproduce the leak
•
Start the emulator and reproduce the
memory leak
…
the emulator will panic
•
Break into Codewarrior
•
Walk back up the stack to
User::__DbgMarkEnd
…
take a note of leaked memory location (badCell)
and thread id.