Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
We're having trouble with a 1st gen iPad not working correctly as of the last couple MonoTouch releases.
The trouble seems somewhat related to IO stalling. The debugger won't connect. Console output does not appear in MonoDevelop until the app is killed, and http streams out of our app are stalling.
Other app-store apps work fine on the device, and our MonoTouch app works fine on other devices, including iPhone 4, and our latest-and-greatest 4th gen ipad.
I like to assume the problem is somehow in our code, but since I can't get MonoDevelop to connect to the application in debug-mode, I'm at a loss for what to do here. (The MonoTouch app starts on the device, but MonoDevelop just hangs on the debug-connect dialog)
I have tried with-and-without SGEN, the ref-counting extension, ARM7 vs ARM7+ARM7s
Hardware Model: iPad1,1 -- Model: MC4977LL, iOS 5.1.1 (9B206)
Host: Mac OS X 10.8.2
EXC_BAD_ACCESS (SIGABRT), KERN_INVALID_ADDRESS at 0x00000008
EXC_BAD_ACCESS (SIGABRT), KERN_INVALID_ADDRESS at 0x0000001c
Created attachment 3301 [details]
I'm not sure if the crash report is relevant or not.
The main issue is that connecting to the debugger doesn't work, and IO is "stalling".
Please note this is iOS 5.1.1, the latest software available for that older device.
The crash report is somewhat strange, the crash itself looks like a fairly common crash - but that crash is not device-dependent, so it doesn't really make things clearer.
Do you have the same problems if you create a new app from a template?
If not, we'd likely need a way to reproduce the behavior you're seeing (a test project or even your entire project if it's easy to reproduce).
We were able to fix the problem with the debugger not-connecting by switching the solution-options "Link" setting from "Don't link" to "Link SDK Assemblies only"... I don't know what the default is, or whether we changed this or not. If we set to "Don't link" the debugger won't connect on iOS 5.1.1 if we set it to "Link SDK assemblies", the debugger connects.
We are still having trouble with HTTP I/O stalling on iOS 5.1.1, but working fine on other releases. Now that the debugger is working, we're digging in to see if we can find a tighter cause and/or make a small reproducable test.
...now that we have debugging working, we tracked the http stall down to a bug in our code.
This means the only potential MonoTouch bug we see, is that if you set project options, "iphone build", "linker behavior" to "don't link"... everything works fine on newer devices, but the debugger won't connect on our iPad 1.1 OS 5.1.1 device.
Can you add -v -v -v to the additional mtouch arguments in the project's iPhone build options, change the linker to "Don't link" and capture the device log output (in MonoDevelop open View -> Pads -> iOS Device Log) from a failed debugging attempt?
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?
If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.
Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.