Bug 36722 - Watchdog in effect during debug
Summary: Watchdog in effect during debug
Alias: None
Product: iOS
Classification: Xamarin
Component: Debugger ()
Version: XI 9.1 (iOS 9.1)
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: (C7)
Assignee: Rolf Bjarne Kvinge [MSFT]
Depends on:
Reported: 2015-12-08 17:34 UTC by timothy.castle
Modified: 2016-05-20 06:32 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description timothy.castle 2015-12-08 17:34:33 UTC
When debugging my app in Xamarin Studio, it keep crashing with the exception 0x8badf00d which indicates that an application has been terminated by iOS because a watchdog timeout occurred according to this link https://developer.apple.com/library/ios/technotes/tn2151/_index.html  However, isn't watchdog supposed to be disabled during debug mode?
Comment 1 Rolf Bjarne Kvinge [MSFT] 2015-12-09 14:01:45 UTC
The watchdog is disabled when debugging using a native debugger (such as lldb).

Xamarin.iOS does not use lldb, so the watchdog is still in effect.

However we're looking at alternatives so that you can debug your launch sequence with the debugger just like you can in Xcode.

In the meantime a potential workaround is to not do anything until you've returned from the FinishedLaunching method (i.e. start your launch code in a timer event for instance), and debug that instead.
Comment 2 Rolf Bjarne Kvinge [MSFT] 2015-12-23 16:21:03 UTC
This has been fixed for the next major release.
Comment 3 Danish Akhtar 2016-05-20 06:32:47 UTC
Hi Timothy,

Could you please provide us your sample application? So that we can verify or reproduce this issue at our end.