View Single Post
Raz0rEdge

 
Raz0rEdge's Avatar
 
Member Since: Jul 17, 2009
Location: MA
Posts: 7,501
Raz0rEdge has a brilliant futureRaz0rEdge has a brilliant futureRaz0rEdge has a brilliant futureRaz0rEdge has a brilliant futureRaz0rEdge has a brilliant futureRaz0rEdge has a brilliant futureRaz0rEdge has a brilliant futureRaz0rEdge has a brilliant futureRaz0rEdge has a brilliant futureRaz0rEdge has a brilliant futureRaz0rEdge has a brilliant future
Mac Specs: 27" i7 iMac, 24" iMac, 13" Macbook Air, iPhone 5 & 5S, iPod Nano 7th Gen, iPad 2 16GB WiFi, iPad 3

Raz0rEdge is offline
Quote:
Originally Posted by Yodda_Hunter View Post
Also it isn't error message.The program just send me to xcode
It *IS* an error message. It's called running Xcode in debug mode and having it go to the line of a code when a problem is detected. In this case, if you look at where you ended up in XCode (albiet assembly code), you see the BAD_ACCESS exception.

You need to look at the stack trace to figure out what functions were being executed and trace your way back step by step to find the culprit code/function/variable/argument/whatever..

Not sure where or what chatterbox is and how you got that code or if you wrote it yourself, but the problem is there..

--
Regards
...Ashwin



Be sure to read the Community Guidelines | The more information you provide, the better answers you get, remember GIGO.
QUOTE Thanks