Bug 43989 - countersonly and onlycoverage options are broken
Summary: countersonly and onlycoverage options are broken
Alias: None
Product: Runtime
Classification: Mono
Component: Profiler ()
Version: master
Hardware: All All
: Normal normal
Target Milestone: 4.8.0 (C9)
Assignee: Alex Rønne Petersen
Depends on:
Reported: 2016-09-04 15:29 UTC by Alex Rønne Petersen
Modified: 2016-10-05 10:54 UTC (History)
1 user (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 GitHub or Developer Community 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 Alex Rønne Petersen 2016-09-04 15:29:18 UTC
The profiler now relies on certain events (thread start, GC STW, etc) to arrive in order to function properly. These options disable those events, and thus cause crashes.

These options have never been documented, though, so it's not entirely clear what should be done with them.
Comment 1 Alex Rønne Petersen 2016-09-09 17:29:04 UTC
Comment 2 Alex Rønne Petersen 2016-10-02 19:52:14 UTC
Fixed: https://github.com/mono/mono/pull/3688
Comment 3 Mohit Kheterpal 2016-10-05 10:54:03 UTC
thanks @Alex

As this issue is filed and fixed by "Alex Rønne Petersen".

Hence closing this issue by marking it as Verified.