Bug 2998 - Exception while executing Stop command
Summary: Exception while executing Stop command
Status: RESOLVED FIXED
Alias: None
Product: iOS
Classification: Xamarin
Component: Debugger ()
Version: 5.0
Hardware: PC Mac OS
: High normal
Target Milestone: Untriaged
Assignee: Rolf Bjarne Kvinge [MSFT]
URL:
Depends on:
Blocks:
 
Reported: 2012-01-20 18:13 UTC by Jackson Harper
Modified: 2012-01-26 18:16 UTC (History)
2 users (show)

Tags:
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:
Status:
RESOLVED FIXED

Description Jackson Harper 2012-01-20 18:13:06 UTC
Exception dialog pops up when stopping the debugger when the app is already closed.  Really no reason to display an error when stopping.


System.InvalidOperationException: Standard input has not been redirected
  at System.Diagnostics.Process.get_StandardInput () [0x00000] in <filename unknown>:0 
  at (wrapper remoting-invoke-with-check) System.Diagnostics.Process:get_StandardInput ()
  at MonoDevelop.IPhone.IPhoneProcess.Cancel () [0x00000] in /Users/builder/data/lanes/monodevelop-mac-2.8.6.2/c83797ae/source/md-addins/MonoDevelop.IPhone/MonoDevelop.IPhone/Execution/IPhoneExecutionHandler.cs:576 
  at MonoDevelop.Core.ProgressMonitoring.AggregatedOperationMonitor.OnCancel (IProgressMonitor m) [0x0002a] in /Users/builder/data/lanes/monodevelop-mac-2.8.6.2/c83797ae/source/monodevelop/main/src/core/MonoDevelop.Core/MonoDevelop.Core.ProgressMonitoring/AggregatedOperationMonitor.cs:68 
  at MonoDevelop.Core.ProgressMonitoring.NullProgressMonitor.OnCancelRequested () [0x0003d] in /Users/builder/data/lanes/monodevelop-mac-2.8.6.2/c83797ae/source/monodevelop/main/src/core/MonoDevelop.Core/MonoDevelop.Core.ProgressMonitoring/NullProgressMonitor.cs:210 
  at MonoDevelop.Core.ProgressMonitoring.NullProgressMonitor.MonoDevelop.Core.IAsyncOperation.Cancel () [0x00000] in /Users/builder/data/lanes/monodevelop-mac-2.8.6.2/c83797ae/source/monodevelop/main/src/core/MonoDevelop.Core/MonoDevelop.Core.ProgressMonitoring/NullProgressMonitor.cs:145 
  at MonoDevelop.Ide.Commands.StopHandler.StopBuildOperations () [0x00037] in /Users/builder/data/lanes/monodevelop-mac-2.8.6.2/c83797ae/source/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Ide.Commands/ProjectCommands.cs:443 
  at MonoDevelop.Ide.Commands.StopHandler.Run () [0x00000] in /Users/builder/data/lanes/monodevelop-mac-2.8.6.2/c83797ae/source/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Ide.Commands/ProjectCommands.cs:435 
  at MonoDevelop.Components.Commands.CommandHandler.Run (System.Object dataItem) [0x00000] in /Users/builder/data/lanes/monodevelop-mac-2.8.6.2/c83797ae/source/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Components.Commands/CommandHandler.cs:61 
  at MonoDevelop.Components.Commands.CommandHandler.InternalRun (System.Object dataItem) [0x00000] in /Users/builder/data/lanes/monodevelop-mac-2.8.6.2/c83797ae/source/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Components.Commands/CommandHandler.cs:42 
  at MonoDevelop.Components.Commands.CommandManager.DefaultDispatchCommand (MonoDevelop.Components.Commands.ActionCommand cmd, MonoDevelop.Components.Commands.CommandInfo info, System.Object dataItem, System.Object target, CommandSource source) [0x00076] in /Users/builder/data/lanes/monodevelop-mac-2.8.6.2/c83797ae/source/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Components.Commands/CommandManager.cs:696 
  at MonoDevelop.Components.Commands.CommandManager.DispatchCommand (System.Object commandId, System.Object dataItem, System.Object initialTarget, CommandSource source) [0x002d1] in /Users/builder/data/lanes/monodevelop-mac-2.8.6.2/c83797ae/source/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Components.Commands/CommandManager.cs:666
Comment 1 Mikayla Hutchinson [MSFT] 2012-01-20 18:22:41 UTC
Is this when debugging an app on a device?
Comment 2 Jackson Harper 2012-01-20 18:24:59 UTC
Yes it was on device. I don't know if it ever even attached properly before the app crashed though.
Comment 3 Jackson Harper 2012-01-20 18:25:29 UTC
Also, FWIW it locked up MD after this, had to kill the process to stop it.
Comment 4 Jackson Harper 2012-01-20 18:28:10 UTC
Sorry, should probably also mention this is MD 2.8.6.2
Comment 6 Jackson Harper 2012-01-20 22:11:48 UTC
Not sure if this effects things but I have been using the xcode console a lot lately because the Application Output doesn't seem to print unhandled exceptions that crash the app anymore.

So maybe this is happening when I am attaching to the console in xcode
Comment 7 Rolf Bjarne Kvinge [MSFT] 2012-01-23 09:52:13 UTC
How did you manage to stop the app while still making MD think it's debugging? If I kill the app, MD will automatically return from debugging mode.
Comment 8 Rolf Bjarne Kvinge [MSFT] 2012-01-26 17:55:09 UTC
Fixed, this exception shouldn't be shown again.
Comment 9 Jackson Harper 2012-01-26 18:16:09 UTC
I am not sure if the exception message is the only problem. It seems like when this happens mtouch also consumes 100% CPU.  I can't figure out exactly how to duplicate though.