https://bugs.winehq.org/show_bug.cgi?id=39674
Bug ID: 39674 Summary: 3Dmark03, 05, 06 not started "Systen Info Error" (double regression) Product: Wine Version: 1.7.55 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: isakov-sl@bk.ru
Created attachment 52897 --> https://bugs.winehq.org/attachment.cgi?id=52897 how the stop looks
Since wine-1.7.55 the Futuremark applications 3DMark03, 3DMark05, 3DMark06 stop working with messages "System Info error" or "unhandled exception". With wine 1.7.54 they are working. Regression test give the follow ~~~ quote ~~~ $ git bisect bad f91a7b2cfe5b44fea333ed70b9fc38a509b7798a is the first bad commit commit f91a7b2cfe5b44fea333ed70b9fc38a509b7798a Author: Austin English austinenglish@gmail.com Date: Wed Nov 4 10:46:50 2015 -0800
fltmgr.sys: Add FltInitializePushLock stub.
Signed-off-by: Austin English austinenglish@gmail.com Signed-off-by: Alexandre Julliard julliard@winehq.org
:040000 040000 9a8f22f1f54f0af7b77216ea29b6360699eacb7e 5185e955c2cb2fe5ca9fa65034af095a9137d23a M dlls :040000 040000 a04028464398c6fceebbbe76e03446a3c2b8cb35 637e2081747c7c533f27d2a0f4ab1258d53bf9fa M include ~~~ quote ~~~
Meanwhile there is double regression as I notice in bug 36548. First regression was 1.7.54 working 1.7.54-140-7fbf33f hang at start. This regression reported and bisecting in 36548. commit 8cc5b07e9d0aedffd4251d2e8942cb8368920bf8
Second regression 1.7.54-134-gd4664c1 works but hang on exit 1.7.55 not working with the message. See attached screenshot. This regression I bisecting here. Strange to see this commit as regression.
Analysis. Then I found a key difference in logs. Working log contains: ---- fixme:process:GetLogicalProcessorInformationEx (65535,0x9f6048,0x8beb54): stub ----
Non-working ---- fixme:process:GetLogicalProcessorInformationEx (65535,0x0,0x5203e8): stub ---- Note: second argument is ZERO.
3DMark application works in conjunction with Futuremarks SystemInfo (called by OLE?) and I may propose the SystemInfo calls the function but in second case it will not allocate buffer for CPU info. BOOL WINAPI GetLogicalProcessorInformationEx(LOGICAL_PROCESSOR_RELATIONSHIP relationship, PSYSTEM_LOGICAL_PROCESSOR_INFORMATION_EX buffer, PDWORD pBufLen) Why? Because there are new stubs? This procedure should return false if no buffer? Or this procedure should allocate this buffer?