In mono_thread_info_suspend_lock in non-coop, don't assert MonoThreadInfo* is non...
authorAleksey Kliger <aleksey@xamarin.com>
Thu, 15 Jun 2017 17:50:10 +0000 (13:50 -0400)
committerAleksey Kliger <aleksey@xamarin.com>
Thu, 15 Jun 2017 17:50:10 +0000 (13:50 -0400)
commit762ac3d618a5eaddedb90362c684fe4aef2cff9a
tree779fcef98de82d375b03a7715c0a92e5b1a732ff
parentbe684e09b478fa3c60d748cfa8b36799a7296b69
In mono_thread_info_suspend_lock in non-coop, don't assert MonoThreadInfo* is non-NULL

mono_thread_info_suspend_lock () can be called from boehm-gc.c
on_gc_notification before the new thread's start_wrapper calls
mono_thread_info_attach but after pthread_create calls the start wrapper.

As a result, the asserts in mono_thread_info_suspend_lock_with_info can catch
the new thread in an inconsistent state.
mono/utils/mono-threads.c