Bug 30 - Lion: Stopping process does not kill the target on the simulator
Summary: Lion: Stopping process does not kill the target on the simulator
Alias: None
Product: iOS
Classification: Xamarin
Component: Debugger ()
Version: 4.x
Hardware: PC Mac OS
: --- major
Target Milestone: Untriaged
Assignee: Rodrigo Kumpera
Depends on:
Reported: 2011-07-20 18:51 UTC by Miguel de Icaza [MSFT]
Modified: 2011-07-28 10:19 UTC (History)
2 users (show)

Tags: lion
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 Miguel de Icaza [MSFT] 2011-07-20 18:51:16 UTC
If you use Run/Stop menu item when an application is run under the debugger under Lion, the application continues to run.

See TweetStation.
Comment 1 Miguel de Icaza [MSFT] 2011-07-22 11:52:21 UTC
This might have been caused because I was still on XCode/SnowLeopard;   But we should at least double test to make sure.

The other side effect was that TweetStation did not respond to any input on the simulator, so it is very likely the mismatch in XCode.
Comment 2 Rodrigo Kumpera 2011-07-28 10:19:49 UTC
I tested this with a local build of what will be 2.10.3 and it works on Lion with 2.4.2. The mismatch is probably the culprit.