[Mono-dev] About your changes to type initialization

Rodrigo Kumpera kumpera at gmail.com
Mon Mar 8 14:24:39 EST 2010

Hi Martin,

On Thu, Mar 4, 2010 at 2:23 PM, Martin Baulig <martin at ximian.com> wrote:

> Ok, I just reverted that revision in trunk and 2.6.
> Ironically, this code now does exactly the right thing when running
> inside a debugger,
> but not when running stand-alone.
> We should consider this a new feature - Thread.Abort() must not abort
> any .cctors
> unless explicitly requested by a debugger.  I'll have a look at this
> next week, once I'm
> done with my Soft Debugger preview version.
Routing Thread::Abort() around is not the behavior I can observe on MS. Do
you have
any test or documentation that shows this behavior? Even if this looks like
the wrong
thing, we should follow MS behavior as compatibility is one of our major

What we could do, thou, is to have this behavior as something our debuggers
can use.

We really need a well defined behavior for debugger initiated thread aborts
because I'm
soon going to implement proper finally block interruption[1]. This can cause
on our debuggers if we don't make clear want everyone needs from the


[1] Under MS, a Thread::Abort is routed around finally blocks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20100308/ce4e1fd0/attachment.html 

More information about the Mono-devel-list mailing list