Debugging uncaught exception in Xcode

Question

I'm trying to get better at using Xcode. I have the AllExceptions break point turned on. When my app crashes, I see this:

*** Terminating app due to uncaught exception 'NSRangeException', reason: '*** -[__NSArrayM objectAtIndex:]: index 1 beyond bounds [0 .. 0]'
*** First throw call stack:
(0xbb8052 0x209cd0a 0xba4db8 0x2255f2 0xc2439 0x12a5e0f 0x12a6589 0x146bfb1 0x147617c 0x12938e1 0x1290602 0x129b211 0x129b23f 0xc16a6 0x138a4c 0x138852 0x14d0e39 0x14d0143 0x14d13cf 0x14d3a31 0x14d398c 0x14cc3e7 0x1234812 0x1234ba2 0x121b384 0x120eaa9 0x28d3fa9 0xb8c1c5 0xaf1022 0xaef90a 0xaeedb4 0xaeeccb 0x28d2879 0x28d293e 0x120ca9b 0x265c 0x25c5)
terminate called throwing an exception(lldb)

On the LHS, when I look at the different threads, I don't see anything that really makes sense. I see some CFRunLoop stuff, but I don't see any "normal" method names like UITableView delegate/datasource methods or my own methods. I was wondering if there was a more informative stack trace available instead of the hex stuff when my app crashes. I know I can set breakpoints at each place I'm accessing the array I think I have a problem with since I'm basically just trying to have an accordion-like tableview with our specific datasource, but I was wondering if there was a faster way by looking at something useful in Xcode. Thanks!

Search for any loops you make in your code and check if you call index our of bounds. you have an array have only one object and you call array[1] — Hossam Ghareeb
– Hossam Ghareeb, Commented Feb 21, 2013 at 22:16
As my experience, i think there is any tool in xcode can help you in this. If you run on device, you can see the log from Organizer and there you may fine more useful Info — Hossam Ghareeb
– Hossam Ghareeb, Commented Feb 21, 2013 at 22:19

Saran · Accepted Answer · 2013-02-21 22:19:29Z

45

In Xcode,

go to Breakpoint navigator on the left pane.
Click '+' at the bottom.
Choose 'Add exception Breakpoint...'
Let the default selections there and click 'Done'.

Rerun the app and see if execution stops at the line which causing this exception.

answered Feb 21, 2013 at 22:19

Saran

6,3923 gold badges41 silver badges49 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

hfossli Over a year ago

Say you have 1000 handled exceptions and you want to find the one uncaught exception, then this isn't helping very much...

Mohammad Sadiq · Accepted Answer · 2020-01-27 06:30:17Z

3

The easiest way to handle the exceptions in XCode during development is to add the exception break points.

You can do that as following.

From left menu select Exceptions navigator

Add the exception break point from bottom left button.

Add break point for all the exceptions

Run the app.

In most of the cases XCode will stop the execution on exception and point at the line that caused the exception.

answered Jan 27, 2020 at 6:30

Mohammad Sadiq

5,23130 silver badges31 bronze badges

Collectives™ on Stack Overflow

Debugging uncaught exception in Xcode

2 Answers 2

1 Comment

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related