Skip to content

Instantly share code, notes, and snippets.

@kmdarshan

kmdarshan/gist:f4bcfc6b5ec7f47a4e014df345924a4f

Created April 2, 2019 05:49
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save kmdarshan/f4bcfc6b5ec7f47a4e014df345924a4f to your computer and use it in GitHub Desktop.
Save kmdarshan/f4bcfc6b5ec7f47a4e014df345924a4f to your computer and use it in GitHub Desktop.
Download ZIP
Detecting a crash in xcode without any stack trace
Raw
gistfile1.txt
Many times you might have observed your app crashing from xcode without any stack trace in the console. This might be due to exceptions.
The easiest way to catch this is through xcode itself.
a. go to your breakpoints/exceptions tab.
b. 'Add Exception Breakpoint' using the + at the bottom left corner.
c. run your code. when the exception hits, you will see the debugger stop.
d. to dig deeper, go to the crashed thread.
e. type 'register read'
f. type 'po $rax'
g. most times, you will see the details here.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment