[PATCH] ntdll: Expand environment variables when querying them

Alexandre Julliard julliard at winehq.org
Tue Mar 26 07:08:48 CDT 2019


Fabian Maurer <dark.shadow4 at web.de> writes:

>> You don't need a reboot, you can test it on a private environment, or
>
>> modify the environment of the current process. In fact we already have
>
>> tests for RtlQueryEnvironmentVariable_U(), and that's how they are
>
>> implemented.
>
> Well, the problem only ever occured when going over the registry,
> that's why I meant I can't test it without reboot Unless I'm missing
> something here, but on windows I can't get the program to get an
> updated environment unless I restart the system.
>
> I did some more testing, and the problem is that Wine populates the
> PEB Environment differently. So the problem is not actually
> RtlQueryEnvironmentVariable_U, but how the environment is loaded from
> the registry. An idea how I would write a test for that?

If the problem is the initial environment, it would be hard to write a
test, yes. FWIW my reading of that bug is that Windows behaves the same
way, except maybe that the registry key order is different. I'm not sure
there's anything to fix here.

-- 
Alexandre Julliard
julliard at winehq.org



More information about the wine-devel mailing list