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.
Every time I try to expand an NSEvent in MonoDevelop, it crashes the underlying Mono runtime (see attached stack trace).
I can reproduce this consistently.
Created attachment 2185 [details]
This could be problematic. It looks like several properties on NSEvent are only valid if the event is of a particular type; if not, then obj-c will throw an exception, which Mono cannot currently handle.
Maybe we could use a debugger proxy object that would return default for those properties if/when the event is not of the correct type.
This is not perfect yet, but here's an implementation which at least fixes this for key and mouse events:
I added [DebuggerBrowsableState.Never] to all the events on the base class, so expanding the "Raw View" will no longer crash.
Still need to test for events other than key or mouse.
So, I'm responding to my past self here, but this has been fixed up in Xamarin.Mac 1.10.
Sorry me for the delay in response.