Looking to allay concerns that I encountered some mysterious armv6 issue:
I spent some time trying to reproduce this in a small test App…the only way
I could break the App was by building the lib with thumb enabled so suspect
I didn't do a full rebuild earlier. It crashes differently than my App
I think I have the same problem, check my post on StackOverflow:
http://stackoverflow.com/questions/8055442/monotouch-error-when-compiling-for-the-device-but-not-on-simulator-mono-patch-i
I've tried many tricks, but I'm still unable to debug on the iPhone.
Only the release with the LLVM compiler
Hello Robert,
I'd say pretty unlikely - but there's something unlikely going on...
but that's a large set of events.
The only way to resolve the mystery is to analyze a test case that
demonstrate the issue.
Regards,
Sebastien
On Mon, Nov 7, 2011 at 7:41 AM, Robert Sweitzer bsw...@gmail.com
Hello Robert,
Is your test case one of the attached files in #707 ? if not the I
would appreciate if you could send us your test case and I'll try to
dig up why your particular case occurs (it should not, unless
something swallow the exception).
It seems there's more than a single issue there
My native library seems to be breaking the non-LLVM armv6 build….LLVM armv7
works fine. However we MUST be able to debug code on the device. I compiled
my (fat) library with LLVM GCC 4.2 and Apple LLVM compiler 3.0. In both
cases running the non-LLVM-nibless armv6 App on my iPad2 throws a
Update: I just upgraded to mtouch 5.0.2.1320356251. Instead of a
NullReferenceException the App now crashes at the same point in my code
with:
Stacktrace:
at MonoTouch.UIKit.UIApplication.Main (string[],string,string) 0x0010f
at Moby.Application.Main (string[]) [0x0] in
