2

For some reason, Xcode is not displaying the line number of the exception, or even the crash itself in the Debugger Output. I have no breakpoints set and it's being built for Debug. The debugger is set to LLDB. I'm not sure how this became onset, but it's badly affecting my workflow now.

How the debugger currently looks.

This isn't how it was before (would display main.m), but I have no idea how it happened.

Giz
  • 199
  • 1
  • 15

1 Answers1

1

Turn off your breakpoints. Up in the top bar, unselect the button labeled Breakpoints.

You likely accidentally clicked on a line and enabled a breakpoint. Additionally, you can click on the button that looks like a play button with a line preceding it to continue the program execution. It is located on the bar above your console output.

rog
  • 5,351
  • 5
  • 33
  • 40
  • With the breakpoints now off, the debugger output now shows the exception. However, the main display in the center of the screen is still not displaying the main.m file as it was before. Is this normal? – Giz May 13 '13 at 20:07
  • `*** Terminating app due to uncaught exception 'NSRangeException', reason: '*** -[__NSArrayM objectAtIndex:]: index 4294967295 beyond bounds [0 .. 12]'` – Giz May 13 '13 at 20:09
  • Now post your code related to the array you're using. Stating the obvious, you're trying to access an object in an array with an invalid index. (Protip: update your original question) – rog May 13 '13 at 20:10
  • The exception shouldn't be the problem however. It shouldn't be displaying this in the center, rather it should be displaying main.m itself. And if I try to use breakpoints, I can't see them in the implementation, which I do need. – Giz May 13 '13 at 20:10
  • Yes, that is true. However, this question is not about the exception itself, rather why Xcode is displaying this output rather than the normal one I have been seeing. – Giz May 13 '13 at 20:11
  • I understand what you're saying now. Interesting, I'm not sure why it'd do that. Try cleaning you're project, I believe I recall seeing a similar question where that was the solution. Cmd + Shift + K – rog May 13 '13 at 20:18
  • let us [continue this discussion in chat](http://chat.stackoverflow.com/rooms/29872/discussion-between-gizmoloon-and-rog) – Giz May 13 '13 at 20:19
  • Not sure if you're still in our chat, so I'll post these suggestions I found here as well: http://stackoverflow.com/questions/5323529/ios-debugging-not-working-in-xcode & http://stackoverflow.com/questions/6333457/xcode-4-not-showing-line-that-debugger-is-stopped-on .. good luck, @Gizmoloon! – rog May 13 '13 at 20:42
  • Nope, sorry, even deleting and redownloading Xcode proved fruitless. – Giz May 13 '13 at 21:34