Failing MODULE_DllProcessAttach causes other module left uninitialized

[Alexandre Julliard]

Uwe Bonnes <bon at elektron.ikp.physik.tu-darmstadt.de> writes:

> I think the original error was obscured to much here. Either we judge a
> failing InitDLL as error and abort there, or in MODULE_DllProcessAttach we
> should recurse without looking at the result.

A failed InitDLL is an error, we can't simply ignore it and
continue. We have to unload the dll and its dependencies in that case;
but that's not entirely trivial to do.

-- 
Alexandre Julliard
julliard at winehq.com