Sure what type of tests would you like to see?
One thing to note is the application I'm referring to Tracker which is part of MS toolchain is a Microsoft application, so no hacks or anything
that copy protection software did that sometimes was not fully compatible with all the loaders changes MS did through out the years.

On Fri, Aug 25, 2017 at 4:41 PM, Alexandre Julliard <julliard@winehq.org> wrote:
Jon Doron <arilou@gmail.com> writes:

> The interesting thing is that in the past Wine behavior was correct
> and the change that basically broke it is commit:
>
> commit 0f5fc117a2320bb7e21b9ae4d07d717bed413171
> Author: Alexandre Julliard <julliard@winehq.org>
> Date:   Mon Nov 19 14:27:07 2007 +0100
>
>     ntdll: Unblock signals in process init only after the dlls have
> been imported.
>
>
> Unfortunately though there I could not find any reason why the change
> was made or if there is any bug that it fixed back then (2007) .

There were apps (usually copy protection) that expected to find some
dlls already loaded in order to patch them. Still, it's very possible
that the initialization order isn't quite correct yet. The first step
would be to write some test cases.

--
Alexandre Julliard
julliard@winehq.org