Hi Guido, This is the important part:
5 libsystem_platform.dylib 0x3bb87720 _sigtramp + 40 6 UIKit 0x3387a12a -[UIPickerView _updateSelectedRows] + 50 7 UIKit 0x3387a26a -[UIPickerView didMoveToWindow] + 74 8 UIKit 0x33609d32 -[UIView(Internal) _didMoveFromWindow:toWindow:] + 1354 9 UIKit 0x33609aa0 -[UIView(Internal) _didMoveFromWindow:toWindow:] + 696 10 UIKit 0x33609aa0 -[UIView(Internal) _didMoveFromWindow:toWindow:] + 696 11 UIKit 0x3362b24a -[UIScrollView _didMoveFromWindow:toWindow:] + 46 12 UIKit 0x33609aa0 -[UIView(Internal) _didMoveFromWindow:toWindow:] + 696 13 UIKit 0x33609aa0 -[UIView(Internal) _didMoveFromWindow:toWindow:] + 696 14 UIKit 0x33609aa0 -[UIView(Internal) _didMoveFromWindow:toWindow:] + 696 15 UIKit 0x3362b24a -[UIScrollView _didMoveFromWindow:toWindow:] + 46 16 UIKit 0x33609aa0 -[UIView(Internal) _didMoveFromWindow:toWindow:] + 696 17 UIKit 0x33609408 __45-[UIView(Hierarchy) _postMovedFromSuperview:]_block_invoke + 108 18 UIKit 0x3360925e -[UIView(Hierarchy) _postMovedFromSuperview:] + 246 19 UIKit 0x338a1a22 __UIViewWasRemovedFromSuperview + 214 20 UIKit 0x33608182 -[UIView(Hierarchy) removeFromSuperview] + 266 21 UIKit 0x336d02c4 -[UINavigationController navigationTransitionView:didEndTransition:fromView:toView:] + 312 22 UIKit 0x3379c1a4 __49-[UINavigationController _startCustomTransition:]_block_invoke + 156 23 UIKit 0x33721ee8 -[_ UIViewControllerTransitionContext completeTransition:] + 72 24 UIKit 0x3387eb08 __53-[_UINavigationParallaxTransition animateTransition:]_block_invoke103 + 448 25 UIKit 0x3364278a -[UIViewAnimationBlockDelegate _didEndBlockAnimation:finished:context:] + 282 26 UIKit 0x336423d2 -[UIViewAnimationState sendDelegateAnimationDidStop:finished:] + 174 27 UIKit 0x336422ea -[UIViewAnimationState animationDidStop:finished:] + 62 An animation stopped (#27), views were moved around (#~20-8), a UIPickerView was moved (#7), something was updated (#6) and then it crashed. I believe this should get you started on tracking it down, most likely it has something to do with the UIPickerView. I would modify my code and see what I'd have to do to make it not crash, and from there try to create a smaller test case. Rolf On Fri, Mar 21, 2014 at 6:57 PM, Guido Van Hoecke <[email protected]> wrote: > Hi Rolf, > > Please find two crashes in appended zip file. > > Tia > > Guido. > > > On 21 March 2014 15:52, Rolf Bjarne Kvinge <[email protected]> wrote: > > Hi, > > > > First get the crash report from Xcode's Organizer [1], this should at > least > > tell us in which direction to look. > > > > Best regards, > > Rolf > > > > [1] Here's how if you've never done it before: > > > http://rolfkvinge.blogspot.com.es/2012/04/native-crashes-in-monotouch.html > > > > > > > > > > On Fri, Mar 21, 2014 at 1:24 PM, Guido Van Hoecke <[email protected]> > wrote: > >> > >> Hi, > >> > >> Our Targister app is available from the app store, the current version > >> 2.2.4 is available since oct 15, 2013. > >> > >> I use it daily to record and control my weight. > >> > >> But recently (last 2 weeks, to my recollection) it starts crashing on my > >> iPhone. > >> > >> So I ran it from the simulator and it indeed crashes when entering the > >> same data that caused crashes on my iPhone (and it is definitely not > >> caused by my weight :). > >> > >> I hoped to get crash data by doing so, but here's all I get in the > >> Xamarin Studio stachk trace: > >> > >> mono-rt: Stacktrace: > >> > >> > >> mono-rt: at <unknown> <0xffffffff> > >> > >> mono-rt: at (wrapper managed-to-native) > >> MonoTouch.UIKit.UIApplication.UIApplicationMain > (int,string[],intptr,intptr) > >> <IL 0x0009f, 0xffffffff> > >> > >> mono-rt: at MonoTouch.UIKit.UIApplication.Main > (string[],string,string) > >> [0x0004c] in > >> /Developer/MonoTouch/Source/monotouch/src/UIKit/UIApplication.cs:38 > >> > >> mono-rt: at ZzLib.Application.Main (string[]) [0x00008] in > >> /Users/guivho/Mono/Targister/Targister/Main.cs:30 > >> > >> mono-rt: at (wrapper runtime-invoke) > <Module>.runtime_invoke_void_object > >> (object,intptr,intptr,intptr) <IL 0x00050, 0xffffffff> > >> > >> mono-rt: > >> Native stacktrace: > >> > >> > >> mono-rt: > >> ================================================================= > >> Got a SIGSEGV while executing native code. This usually indicates > >> a fatal error in the mono runtime or one of the native libraries > >> used by your application. > >> ================================================================= > >> > >> > >> Please advise about how to go about to pinpoint this problem. > >> > >> Tia, > >> > >> > >> Guido > >> > >> -- > >> moon, n: > >> 1. A celestial object whose phase is very important to > >> hackers. See PHASE OF THE MOON. 2. Dave Moon (MOON@MC). > >> _______________________________________________ > >> MonoTouch mailing list > >> [email protected] > >> http://lists.ximian.com/mailman/listinfo/monotouch > > > > > > > > > > -- > > Explore Xamarin University--unlimited, live, online, mobile training > around > > the clock. > -- Explore Xamarin University <http://xamarin.com/university>--unlimited, live, online, mobile training around the clock.
_______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
