[Mono-dev] mono_thread_manage causes subsequent mono_jit_cleanup call to hang?

Rodrigo Kumpera kumpera at gmail.com
Fri Sep 12 05:47:35 UTC 2014


How about internally renaming mono_thread_manage and add a no-op version of
it.

It would retain compatibility with wine and would not further complicate
the shutdown sequence.

This assumes that there's no good use case for calling the two
independently.

--
Rodrigo

On Wed, Sep 10, 2014 at 5:58 PM, Vincent Povirk <madewokherd at gmail.com>
wrote:

> > 2. Should Mono be fixed to account for what I was doing? I'd prefer to
> > have code that is as version-independent as possible. Maybe mono could
> > somehow detect that mono_thread_manage was already completed by the
> > current thread, and do nothing in this case?
>
> I wrote a patch using this approach:
>
> https://github.com/madewokherd/mono/commit/7baf38fd134f92f7d80f43bb3cf6d77122b3eb1e
>
> But I'm really not sure about this.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20140912/6e3cf358/attachment.html>


More information about the Mono-devel-list mailing list