July 2019 - Wine-Devel - list.winehq.org

Re: [PATCH] msi: Close all handles opened by a custom action thread.

by Hans Leidekker

Signed-off-by: Hans Leidekker <hans(a)codeweavers.com>

July 1, 2019

[PATCH] ntdll: Add '-norelay' flag for _vsnprintf().

by Dmitry Timoshkov

Otherwise for instance +relay,+ver log has ver: traces completely messed up. Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> --- dlls/ntdll/ntdll.spec | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dlls/ntdll/ntdll.spec b/dlls/ntdll/ntdll.spec index 0ec7b56c2b..94bc52cc14 100644 --- a/dlls/ntdll/ntdll.spec +++ b/dlls/ntdll/ntdll.spec @@ -1419,7 +1419,7 @@ @ cdecl _ui64tow(int64 ptr long) @ cdecl _ultoa(long ptr long) @ cdecl _ultow(long ptr long) -@ cdecl _vsnprintf(ptr long str ptr) NTDLL__vsnprintf +@ cdecl -norelay _vsnprintf(ptr long str ptr) NTDLL__vsnprintf @ cdecl _vsnwprintf(ptr long wstr ptr) NTDLL__vsnwprintf @ cdecl _wcsicmp(wstr wstr) NTDLL__wcsicmp @ cdecl _wcslwr(wstr) NTDLL__wcslwr -- 2.20.1

July 1, 2019

Re: Profiling application under Wine

by Hin-Tak Leung

This is the relevant part of the documentation. So presumably you can do MONO_ENV_OPTIONS="--profile" and MONO_ENV_OPTIONS="--profile=stuff" , I believe. === DEVELOPMENT OPTIONS ... --profile[=profiler[:profiler_args]] Loads a profiler module with the given arguments. For more information, see the PROFILING section. This option can be used multiple times; each time will load an additional profiler module. ENVIRONMENT VARIABLES ... MONO_ENV_OPTIONS This environment variable allows you to pass command line arguments to a Mono process through the environment. This is useful for example to force all of your Mono processes to use LLVM or SGEN without having to modify any launch scripts. === On Friday, 28 June 2019, 19:09:22 BST, Vincent Povirk <madewokdev(a)gmail.com> wrote: The WINE_MONO_* variables are just the ones we've added. Other MONO_* variables should generally work the same as in regular Mono. I haven't worked with Mono's profiling tools so I can't give any further advice. On Fri, Jun 28, 2019, 11:18 AM Hin-Tak Leung <htl10(a)users.sourceforge.net> wrote: Hmm, I think wine-mono has been working in 64-bit mode for a while - although you have to invoke wine explicitly as wine64 to hook into it . I think there are some quirks about how wine and wine-mono interacts, in such a way that you cannot do 32-bit + 64-bit switches within the process - i.e. you must do 64-bit wine to get at 64-bit wine-mono. Do you notice any performance difference between using wine-mono and dotnet472 64-bit ? I am going back to wine-mono for your issue, as mono supports setting profiling option via environment variables (catering for exactly this use case, when mono is running embedded inside another process), and you can set WINE_MONO_* variables to pass those along. I am not sure about the exact details so you'll need to look up the relevant docs, but I know this is possible - mono has a built-in profiler, and it is accessible and turned on via environment variables. -------------------------------------------- On Tue, 25/6/19, Chambers, Matthew <matt.chambers42(a)gmail.com> wrote: The application requires dotnet472 and 64-bit at that. I actually had to add that verb to winetricks to get our application to work. I'm definitely getting varying mileage! My question is how to profile it with Windows symbols so I can understand why and either help fix it in Wine or possibly avoid the problem from my application code.

July 1, 2019