http://bugs.winehq.org/show_bug.cgi?id=16491
--- Comment #9 from Anastasius Focht focht@gmx.net 2010-06-15 15:33:00 --- Hello,
--- quite --- Anastasius, how did you get this nice CLR trace? Could you please post some update for that, cause initial problem with empty date values is fixed I think. --- quite ---
It's the Framework itself that displays the dialog with CLR backtrace and assemblies list. See http://msdn.microsoft.com/en-us/library/2ac5yxx6%28VS.80%29.aspx or google "DbgJITDebugLaunchSetting" for further information.
One can also intercept/trap these exceptions by using managed CLR debuggers like mdbg or cdb (with mscorwks sos debugging extension) from "Debugging Tools for Windows".
As comment #4 already stated it freezes when advancing months. Seems there is some heap corruption caused by double free when handling reflected messages/commands (+tid,+seh,+relay,+loaddll,+heap,+win,+msg,+monthcal).
Regards