wine-devel August 2015

wine-devel@winehq.org

59 participants
198 discussions

IDirect3DRMTexture stub patches.
by Aaryaman Vasishta 24 Aug '15

24 Aug '15

These patches will be needed before I can add tests for, and implement version 1 of Create/LoadTexture. Please provide feedback on any modifications required. (Patches 0000-0006 are already in wine-patches but not committed yet). Cheers, Jam

2 2

Re: [PATCH] ucrtbase: Add the new universal CRT DLL.
by Alexandre Julliard 24 Aug '15

24 Aug '15

Martin Storsjo <martin(a)martin.st> writes: > +@ stub -arch=win32 ?_set_new_handler@@YAP6AHI@ZH@Z # int(__cdecl*__cdecl _set_new_handler(int))(unsigned int) > +@ stub -arch=win64 ?_set_new_handler@@YAP6AH_K@ZH@Z # int(__cdecl*__cdecl _set_new_handler(int))(unsigned __int64) > +@ stub _set_new_mode > +@ cdecl _set_printf_count_output(long) MSVCRT__set_printf_count_output > +@ cdecl _set_purecall_handler(ptr) > +@ stub -arch=win32 ?_set_se_translator@@YAP6AXIPAU_EXCEPTION_POINTERS@@@ZH@Z # void(__cdecl*__cdecl _set_se_translator(int))(unsigned int,struct _EXCEPTION_POINTERS *) > +@ stub -arch=win64 ?_set_se_translator@@YAP6AXIPEAU_EXCEPTION_POINTERS@@@ZH@Z # void(__cdecl*__cdecl _set_se_translator(int))(unsigned int,struct _EXCEPTION_POINTERS * __ptr64) I don't see any mangled names in my version. -- Alexandre Julliard julliard(a)winehq.org

2 1

Re: winhttp: Add support for WinHttpRequestOption_URLCodePage.
by Hans Leidekker 24 Aug '15

24 Aug '15

On Mon, 2015-08-24 at 15:03 +0800, Dmitry Timoshkov wrote: > @@ -3071,6 +3072,7 @@ static void initialize_request( struct winhttp_request *request ) > request->connect_timeout = 60000; > request->send_timeout = 30000; > request->receive_timeout = 30000; > + request->url_codepage = CP_ACP; MSDN says that it defaults to CP_UTF8 and my tests confirm that.

1 0

Re: ieframe: Added more test traces to diagnose some test failures.
by Marvin 23 Aug '15

23 Aug '15

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://testbot.winehq.org/JobDetails.pl?Key=16243 Your paranoid android. === w2000pro (32 bit webbrowser) === webbrowser.c:2971: Test failed: expected Invoke_COMMANDSTATECHANGE_NAVIGATEBACK_FALSE webbrowser.c:2976: Test failed: expected Invoke_COMMANDSTATECHANGE_NAVIGATEFORWARD_FALSE webbrowser.c:2971: Test failed: expected Invoke_COMMANDSTATECHANGE_NAVIGATEBACK_FALSE webbrowser.c:2976: Test failed: expected Invoke_COMMANDSTATECHANGE_NAVIGATEFORWARD_FALSE webbrowser.c:2971: Test failed: expected Invoke_COMMANDSTATECHANGE_NAVIGATEBACK_FALSE webbrowser.c:2976: Test failed: expected Invoke_COMMANDSTATECHANGE_NAVIGATEFORWARD_FALSE

1 0

Re: [3/4] ntdll/tests: Add additional tests for calling NtOpenFile with file object as RootDirectory.
by Marvin 23 Aug '15

23 Aug '15

1 0

Re: gdi32/tests: 64 bit GetFontFileInfo may fail with error ERROR_NOACCESS.
by Marvin 22 Aug '15

22 Aug '15

1 0

Re: different behaviors of mixed-mode assembly under .net/wine-mono/native mono.
by Hin-Tak Leung 22 Aug '15

22 Aug '15

------------------------------ On Sat, Aug 22, 2015 5:07 PM BST Vincent Povirk wrote: >> Is it possible to enable win32 mono's mixed mode support at runtime, >> or does it requires a re-compile? > >I'm not sure, but I think there is a switch to mono.exe. > Hmm, I just read the linux mono man pages... don't know where the win32-specfic features of mono might be documented. I'll try to find out. >> The two ldarg.s look invalid to me, but it is possible that Cecil is getting >> confused in the same way as mono. > >The solution is probably to modify the JIT compiler in wine-mono to >accept this code. If you feel like looking into this issue, the application concerned is Microsoft's font validator: https://www.microsoft.com/typography/FontValidator.mspx The LTSH and hdmx, vdmx table tests and the rasterization test (on a different tab) throws illegal IL code exception captured in its report. You can de-select the other tests which don't matter. To use, click "add font" under the options, load up any truetype font, and click the 'tick" symbol to start. The XML viewer doesn't work under wine - COM/ActiveX and IE - so you probably want to save the report and read it as text. The exceptions are thrown in the truetype.dll as: Invalid IL code in Avalon.Media.Text.TrueType.RasterInterf:CalcDevMetrics (int,int,int,uint16,byte[],uint16,byte,byte,uint16[],uint16[],uint16,Avalon.Media.Text.TrueType.RasterInterf/UpdateProgressDelegate): IL_039a: ldarg.s Invalid IL code in Avalon.Media.Text.TrueType.RasterInterf:RastTest (int,int,int[],single,single,single,single,single[2],Avalon.Media.Text.TrueType.RasterInterf/RastTestErrorDelegate,Avalon.Media.Text.TrueType.RasterInterf/UpdateProgressDelegate): IL_0098: ldarg.s if you don't even want to run it :-). As I said it works correctly under wine + .net 2, and throws the "correct" error under linux mono and win32 mono about not being able to initialize the constructor of an object around native code, so both behaviors are "expected". I have a command-line wrapper around the Font Validator to make batch testing easier, though I don't expect it is of any use for looking at the IL code issue?

1 2

Re: [3/3] ntdll: Implement FileRenameInformation support. (try 2)
by Marvin 22 Aug '15

22 Aug '15

1 0

Re: different behaviors of mixed-mode assembly under .net/wine-mono/native mono.
by Hin-Tak Leung 22 Aug '15

22 Aug '15

------------------------------ On Fri, Aug 21, 2015 8:20 PM BST Vincent Povirk wrote: >> So I have a specific question - how do I go about finding >> out how the IL code exception comes about? >> (I have had a couple of patches in either camp so >> I am not against patching wine or mono, or wine-mono for that matter) > >You can set the WINE_MONO_VERBOSE environment variable to a single >digit greater than 0 to get debugging information related to JIT >compilation. This should at least tell you exactly which method's IL >is being rejected. > Actually I don't need that - the applicatin itself records the stack trace in its normal xml output as: Invalid IL code in method1 (int,int,int,uint16,byte[],uint16,byte,byte,uint16[],uint16[],uint16, delegate type1): IL_039a: ldarg.s 12

 and Invalid IL code in method2 (int,int,int[],single,single,single,single,single[2],delegate type1, delegate2): IL_0098: ldarg.s 8

 The first one is doing "ldarg.s <the delegate>", while the other is doing "ldarg.s <the single[2]>". I just noticed one anomaly - the single[2] type should be a single[,] type; These are according to monodevelop's assembly browser. >Setting MONO_VERBOSE_METHOD will show debugging information for the >JIT compilation of a specific method, unfortunately Mono crashes >trying to parse many of the mangled names that appear in Managed C++ >assemblies, so often this approach does not work for me. I've often >had to hack the code that checks MONO_VERBOSE_METHOD to special-case a >specific method name. > monodis somehow doesn't show either of those. >> And a general question: are mixed mode assemblies supposed >> to work under win32 mono at all, or wine-mono definitely needed? >> I saw some wine + mono discussions a while ago and >> I got the impression that mixed mode assemblies are supposed to >> work with win32 mono somewhat? > >There is some support for mixed-mode in win32 mono, but it is disabled >by default. They are different enough that I would not use win32 mono >on Windows to learn anything about how well wine-mono "should" work. > Is it possible to enable win32 mono's mixed mode support at runtime, or does it requires a re-compile? >> The application itself is available as a public download in binary form. >> But since it mostly works - correctly under .net, and even the >> illegal IL exception was caught, just not the null constructor. >> Editing the IL code to put a try+catch around the constructor >> makes it largely operational too under linux mono, so there is >> not much of a bug to file; mostly a curiosity why >> wine-mono doesn't behave like it support mixed-mode fully, or >> not at all, but something between. > >Microsoft's managed C++ compiler has been known to generate IL that >technically violates ecma 335, or otherwise gives Mono trouble. We >have hacks in wine-mono for a few of these cases, but it's likely we >have not addressed all of them. > >There are also features used by managed C++, such as "thiscall" >reverse-pinvokes, which are technically independent of mixed-mode, but >which are not implemented in wine-mono. The two ldarg.s look invalid to me, but it is possible that Cecil is getting confused in the same way as mono.

2 1

Re: [2/4] ntdll/tests: Add additional tests for FileRenameInformation.
by Marvin 21 Aug '15

21 Aug '15

1 0

← Newer
1
...
4
5
6
7
8
9
10
...
20
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel August 2015