application crash with last sugarcube update

yestoall commented 10 years ago

last updates doesn't work for me: invisible error in the terminal and application crash.

compiling with RM 2.17 and sugarcube 1.3.7 everything works perfect.

anyone else?

yestoall commented 10 years ago

compiling my application with sugarcube greater than 1.3.7 always crash in the simulator with no error in the terminal. always in the same point: scrolling a tableview, always without errors.

with sugarcube 1.3.7 works perfect.

any ideas?

yestoall commented 10 years ago

i can't resolve this issue

compiling with RM 2.12 and last sugarcube i'm having this error with rake debug=1

Process 15063 stopped

thread #1: tid = 0x1d65f, 0x013590b2 libobjc.A.dylibobjc_msgSend + 14, queue = 'com.apple.main-thread, stop reason = EXC_BAD_ACCESS (code=1, address=0x3000000c) frame #0: 0x013590b2 libobjc.A.dylibobjc_msgSend + 14 libobjc.A.dylib`objc_msgSend + 14: -> 0x13590b2: movzwl 12(%edx), %eax 0x13590b6: andl %ecx, %eax 0x13590b8: shll $3, %eax 0x13590bb: addl 8(%edx), %eax

colinta commented 10 years ago

I'm not ignoring you here, it's just that there's very little to go on here. On my system I don't get any errors... do you get any clues by using > rake debug and running > bt when it crashes?

I need you to isolate what code is causing the error, otherwise I really can't help. :-/

yestoall commented 10 years ago

thank you for not ignoring me :)

what's bt?

i'm trying to see where exactly my app is crashing writing in the console, but i've not clues for now

colinta commented 10 years ago

bt is the backtrace command in the debugger.

> rake debug=1  # run the app using the debugger
...
  Simulate ./build/iPhoneSimulator-7.0-Development/Your App.app
1 location added to breakpoint 1
1 location added to breakpoint 2
(lldb)

When your app crashes, it'll look like this:

2013-12-19 08:40:04.661 Your App[5512:70b] *** Terminating app due to uncaught exception 'RuntimeError', reason: 'app_delegate.rb:10:in `application:didFinishLaunchingWithOptions:': foo (RuntimeError)
'
*** First throw call stack:
(
    0   CoreFoundation                      0x060bd5e4 __exceptionPreprocess + 180
...
-> 0x770a952:  jae    0x770a962                 ; __pthread_kill + 26
   0x770a954:  calll  0x770a959                 ; __pthread_kill + 17
   0x770a959:  popl   %edx
   0x770a95a:  movl   26311(%edx), %edx
(lldb)

Now you can run bt

(lldb) bt
* thread #1: tid = 0x5a748a, 0x0770a952 libsystem_kernel.dylib`__pthread_kill + 10, queue = 'com.apple.main-thread, stop reason = signal SIGABRT
    frame #0: 0x0770a952 libsystem_kernel.dylib`__pthread_kill + 10
    frame #1: 0x076ce167 libsystem_pthread.dylib`pthread_kill + 101
    frame #2: 0x073e0e12 libsystem_sim_c.dylib`abort + 127
    frame #3: 0x072b39f9 libc++abi.dylib`abort_message + 105

Sometimes - not always - there's something useful in there.

yestoall commented 10 years ago

how can i install backtrace?

yestoall commented 10 years ago

sorry, stupid question; i'm playing with bt right now thanks ;)

yestoall commented 10 years ago

after 4 hours of research i've found a solution for the problem. but i don't understand exactly why ;)

in my project i'm working with quite complex UITableViewCell (complex because they have a los of subview, and gesture behaviours)

debugging the crash report i've found that always crash with deallocating memory of some subviews, subviews of MDHTMLLabel pod. i've changed all this HDHTMLLabel with UILabel and now it's working. but i think is not a specific problem of this pod, because it works pretty good in with RM 2.16 and sugarcube 1.3.7 i think is a RM problem but i don't really understand why.

thanks again for your code and for your help. sorry for my english, my spanish is better ;)

rubymotion-community / sugarcube

application crash with last sugarcube update #109