Re: help with debugging

2014-11-18 Thread KappA
Just a thought off the top (please excuse me if I'm far off)... but what about wrapping in a @try/@catch to handle the exception and get more details? Again, sorry if I'm far off, still having my first cup of coffee. https://developer.apple.com/library/ios/documentation/Cocoa/Conceptual/Exceptions

Re: help with debugging

2014-11-18 Thread Sean McBride
On Tue, 18 Nov 2014 10:25:07 -0800, Jens Alfke said: >> Those offsets tell you how far into the function (in bytes I think) it >was. You can indeed bring that back to a line number. See here: >> >> symbolication.html>> > >That inf

Re: help with debugging

2014-11-18 Thread Jens Alfke
> On Nov 18, 2014, at 10:04 AM, Sean McBride wrote: > > Those offsets tell you how far into the function (in bytes I think) it was. > You can indeed bring that back to a line number. See here: > > > That in

Re: help with debugging

2014-11-18 Thread Sean McBride
On Wed, 19 Nov 2014 00:52:13 +0700, sqwarqDev said: >0 CoreFoundation 0x7fff8cd5664c >__exceptionPreprocess + 172 > 1 libobjc.A.dylib 0x7fff975c86de >objc_exception_throw + 43 > 2 CoreFoundation 0x7fff8cd56

help with debugging

2014-11-18 Thread sqwarqDev
Hi folks Pretty uneducated in anything other than the basics of debugging, so I have a bug in my app which I can't reproduce my end, but I get several user reports that all show the same console.log errors. The bug is near-fatal, i.e. doesn't crash the app, but stops it displaying a window cont