Hi, Sorry, I didn't realize this is happening on the device.
For device you can use this trick to force quit, which will generate a crash report: "Force quits occur when the user first holds down the On/Off button until "slide to power off" appears, then holds down the Home button." (from here: http://developer.apple.com/library/ios/#technotes/tn2151/_index.html) Rolf On Mon, Jul 30, 2012 at 1:05 PM, Dermot O Sullivan <[email protected]> wrote: > Ok, have tried to do this but didn't get very far. > Froze up, but no Program ID info in MonoDevelop Application Output. In > Xcode console, This is what I have: > > Jul 30 20:53:51 unknown com.apple.debugserver-64[6966] <Warning>: > debugserver-64 for armv6 Copyright (c) 2007-2009 Apple, Inc. All Rights > Reserved. > Jul 30 20:53:51 unknown com.apple.debugserver-64[6966] <Warning>: > Connecting to com.apple.debugserver service... > Jul 30 20:53:51 unknown com.apple.launchd[1] <Warning>: > (UIKitApplication:com.groovepond.app[0x4710]) Spawned and waiting for the > debugger to attach before continuing... > Jul 30 20:53:51 unknown com.apple.debugserver-64[6966] <Warning>: Got a > connection, waiting for debugger instructions for task "(null)". > Jul 30 20:53:51 unknown com.apple.debugserver-64[6966] <Warning>: 1 > [1b36/1303]: error: ::read ( 4, 0x2ff609d4, 1024 ) => -1 err = Bad file > descriptor (0x00000009) > Jul 30 20:53:51 unknown com.apple.debugserver-64[6958] <Warning>: 1 > [1b2e/0303]: error: ::read ( 4, 0x2fe1c4b0, 1024 ) => 0 err = Bad file > descriptor (0x00000009) > Jul 30 20:53:51 unknown mobile_installation_proxy[6962] <Error>: main: > Could not receive request from host. > Jul 30 20:53:51 unknown mobile_installation_proxy[6955] <Error>: main: > Could not receive request from host. > Jul 30 20:53:52 unknown kernel[0] <Debug>: lockbot[6949] Builtin profile: > debugserver (sandbox) > Jul 30 20:53:52 unknown kernel[0] <Debug>: launchd[6967] Builtin profile: > container (sandbox) > Jul 30 20:53:52 unknown kernel[0] <Debug>: launchd[6967] Container: > /private/var/mobile/Applications/FEEC09F1-ADBD-4605-9E63-11B64257189C [69] > (sandbox) > Jul 30 20:54:20 unknown lockdownd[26] <Error>: libMobileGestalt > computeUniqueDeviceID: total time for bb to return imei: 0 > Jul 30 20:54:20 unknown lockdownd[26] <Notice>: 015d4000 copy_phonenumber: > CTSettingCopyMyPhoneNumber() returned NULL > Jul 30 20:54:21 unknown lockdownd[26] <Error>: libMobileGestalt > computeUniqueDeviceID: total time for bb to return imei: 0 > Jul 30 20:54:21 unknown lockdownd[26] <Notice>: 015d4000 copy_phonenumber: > CTSettingCopyMyPhoneNumber() returned NULL > > > Jul 30 20:54:21 unknown DTFetchSymbols[6977] <Notice>: Found paths: > Jul 30 20:54:21 unknown DTFetchSymbols[6977] <Notice>: /usr/lib/dyld > Jul 30 20:54:21 unknown DTFetchSymbols[6977] <Notice>: > /System/Library/Caches/com.apple.dyld/dyld_shared_cache_armv7 > Jul 30 20:54:21 unknown DTFetchSymbols[6977] <Notice>: > /Developer/usr/lib/CFDataFormatters.dylib > Jul 30 20:54:21 unknown DTFetchSymbols[6977] <Notice>: > /Developer/usr/lib/libdebugnub.dylib > Jul 30 20:54:21 unknown DTFetchSymbols[6977] <Notice>: > /Developer/usr/lib/libXcodeDebuggerSupport.dylib > > > Jul 30 20:54:21 unknown DTFetchSymbols[6977] <Notice>: > /Developer/Library/PrivateFrameworks/GPUTools.framework/libglInterpose.dylib > Jul 30 20:54:21 unknown DTFetchSymbols[6977] <Notice>: > /Developer/Library/PrivateFrameworks/GPUToolsCore.framework/GPUToolsCore > Jul 30 20:54:21 unknown DTFetchSymbols[6977] <Notice>: > /Developer/Library/PrivateFrameworks/DevToolsBundleInjection.framework/DevToolsBundleInjection > Jul 30 20:54:21 unknown DTFetchSymbols[6977] <Notice>: > /Developer/Library/Frameworks/SenTestingKit.framework/SenTestingKit > > > > I tried to gdb all PIDs mentioned (6977 etc...) and got the error below: > > MacbookAir:~ Dermot$ gdb program <6977> > -bash: syntax error near unexpected token `6977' > MacbookAir:~ Dermot$ gdb program 6977 > GNU gdb 6.3.50-20050815 (Apple version gdb-1708) (Mon Aug 8 20:32:45 UTC > 2011) > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you > are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "x86_64-apple-darwin"...File 'program' does not > exist or is not a regular file. > > /Users/Dermot/6977: No such file or directory > Unable to access task for process-id 6977: (os/kern) failure. > > On Mon, Jul 30, 2012 at 1:55 AM, Rolf Bjarne Kvinge <[email protected]>wrote: > >> Hi, >> >> On Sat, Jul 28, 2012 at 3:50 AM, dermotos <[email protected]> wrote: >> >>> Does anyone else experience random lockups/freezes of their app when >>> debugging? >>> >>> It may indeed be some deadlocks in my code, but before I go hunting for >>> them >>> I thought id check incase maybe its a debugger issue. >>> Strange thing is it only seems to happen when debugging, but I know from >>> experience that issues like deadlocks/race conditions etc can often >>> happen >>> when the debugger is attached, simply because it may slow down certain >>> parts >>> of the code, and cause the issue to manifest itself (rather than being an >>> actual problem with the debugger). >>> >> >> There have been several bugs with the debugger that causes lockups / >> freezes, but it could also be your own code. >> >> The easiest way to determine this is to get a native stack trace for all >> threads for the app: >> >> Find the pid of the app - it is printed to the application output in >> MonoDevelop at startup. >> >> Then execute from a terminal: >> >> > gdb program <PID> >> (gdb will attach, some output until a gdb prompt appears:) >> $(gdb) thread apply all backtrace >> (gdb will print stack traces for all threads). >> >> Get all the output from the terminal, save it to a file and send it to >> the lists, and we'll easily be able to figure out if it's a deadlock in >> your code or if it's in the debugger. >> >> Rolf >> >> >>> >>> >>> >>> -- >>> View this message in context: >>> http://monotouch.2284126.n4.nabble.com/lockups-during-debugging-or-deadlocks-in-my-code-tp4656215.html >>> Sent from the MonoTouch mailing list archive at Nabble.com. >>> _______________________________________________ >>> MonoTouch mailing list >>> [email protected] >>> http://lists.ximian.com/mailman/listinfo/monotouch >>> >> >> >
_______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
